> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# GitHub (Copilot)

> Learn how to configure Docusign MCP server in GitHub (Copilot).

Follow the steps below to configure your Docusign MCP server, starting with the required prerequisites and credentials.

## Prerequisites

Before connecting to the Docusign MCP server, you will need:

* A Docusign developer account. You can [create one](https://www.docusign.com/developers/sandbox) for free at the [Developer Center](/).
* Integration key id - See Configure your app to add an  [Integration key](/platform/configure-app#integration-key).
* Client secret - See Configure your app to create a [secret key](/platform/configure-app#secret-key).

## App Configuration

1. Obtain an Integration Key (IK). Refer [How to get an integration key](/platform/configure-app#how-to-get-an-integration-key) page.
2. Generate a client secret. Refer [How to add a secret key](/platform/configure-app#how-to-add-a-secret-key) page.
3. Enter the following redirect URLs for your app. Refer [How to set a redirect URI](/platform/configure-app#how-to-set-a-redirect-uri) page.

| Purpose                          | URI                                                        |
| -------------------------------- | ---------------------------------------------------------- |
| VS Code localhost authentication | [http://127.0.0.1:33418](http://127.0.0.1:33418)           |
| VS Code Web authentication       | [https://vscode.dev/redirect](https://vscode.dev/redirect) |

![redirect-uri-vs-code-mcp](/_fern-files/_img/3f4feb01678647a54147b3c8f61fcf2cd4c74d267b41e615f60fcc139b3c50a3.webp)

### Adding a MCP server in VS Code

To add a MCP server in VS Code:

1. Launch Microsoft Visual Studio Code.
2. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P).
3. Select **MCP: Add Server…** command.
4. Select **HTTP (HTTP or Server-Sent-Events)**  protocol.
5. Enter Server URL as **[https://mcp-d.docusign.com/mcp](https://mcp-d.docusign.com/mcp)** and press Enter.
6. Enter a **Server ID** name and press Enter. For example: Docusign-MCP.
7. Select configuration target as either **Global** or **Workspace**.
8. At the top of your JSON file, you’ll see a small toolbar above your configuration as **Start | nn tools | More...** Click **Start** to launch the MCP server.

   ![docusign-mcp-server-start](/_fern-files/_img/87007ba9cf62cd3929b6a31b6d8ea5b43550714852eeae2f575daac3c62f2e90.webp)
9. Select **Copy URIs & Proceed** in the popup window.
10. Enter the **Integration Key (IK)** of the app and press Enter.
11. Enter the **client secret** of the app and press Enter.
12. Select **Allow** to authenticate the Docusign MCP server.
13. Sign in to your Docusign account in your browser.
14. Select Open Visual Studio Code.

### Verify the MCP server is ready for use

Open the Copilot chat box, then select the **Configure Tools** button to see available tools. You should see all of the available tools within the Docusign MCP server.

![Step 4 Verify the MCP Server](/_fern-files/_img/a5e9822144e76c9989d2eb27db7fe6e9aef7f92270fa5b21c31c791148efd4f1.webp)

### Run a test prompt

Verify the MCP connection by entering a prompt such as: “Can you list the Docusign tools available to me?”

**Note**: The wording of AI responses may differ between AI platforms, but the data and results should be the same.

![Step 5 Run a Test Prompt](/_fern-files/_img/d1cb78765f41a9afcfcb5199837dd254db3c943daef58219437d1b88de75be42.webp)

## Remove MCP Configuration in VS Code

To remove an existing MCP server in VS Code:

1. Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P).
2. Select **Authentication: Remove Dynamic Authentication Providers** command.
3. Select **mcp-d.docusign.com** and select OK.
4. Select **Remove** to confirm.

## Next steps

* Try the [Docusign Developer AI Assistant for VS Code (Beta)](/tools/ai-assistant-vs-code) to generate access tokens, orchestrate APIs, and get real-time answers to Docusign integration questions directly in your IDE.
* Try the Docusign MCP server with [Anthropic (Claude)](/platform/mcp-server/anthropic-claude) to explore its capabilities.