> 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 # Anthropic (Claude) > Learn how to configure Docusign MCP server in Anthropic (Claude). ## 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](/). * Anthropic Claude account. ## Authentication Docusign MCP server supports both **Confidential Authorization Code Grant (ACG)** and **JSON Web Token (JWT)** OAuth grant types. The following procedure uses ACG authentication type. With Claude you can use one of the methods based on the following: * User type * Docusign environment (Demo and production) ## Custom Connector Method Before adding a custom connector to Claude, you must first create an application within your Docusign [Apps and Keys](https://apps-d.docusign.com/admin/apps-and-keys) page. Please ensure you complete the following steps before configuring the MCP (Model Context Protocol) server: 1. **Create an App:** Generate a new application and copy the **Integration Key (IK).** 2. **Generate a Secret:** Add a **Client Secret** and copy the value immediately (it will not be visible later). 3. **Set Redirect URIs:** Configure the following **Redirect URI** within the app settings to ensure proper authentication. 1. 2. ### Setup Procedure Follow the process below to complete these configuration steps: 1. Go to the [Apps and Keys](https://apps-d.docusign.com/admin/apps-and-keys) of your Docusign developer or production account. 2. Select **Add App and Integration Key**. 3. Create a new IK with your desired name (example: “Claude Cowork”). 4. Copy the **Integration Key** value. 5. Select **Add Secret Key** (it will not be visible later). 6. Select **+ Add URI** and add the following two URIs in **Redirect URIs** section: * [](https://claude.ai/api/mcp/auth_callback) * [](https://claude.com/api/mcp/auth_callback) ![gif for adding redirect uris](/_fern-files/docusign.docs.buildwithfern.com/be4f60f899e44d3e482131be39c5f6c275dd577ab4537e7a8bde2f7e4cdadc96/assets/img/ctf/2S5jd2OLR5sPCAD7TgqKsS-Add_Redirect_URI.gif) ### Step 1. Open Claude Desktop Go to **Avatar** > **Settings** > **Connectors** and select **Add**. ![Claude desktop screenshot](/_fern-files/_img/eba1041a0be8a461a8db2d7ceaf04f28c19d698136551ff5a8d3497aa4f93c73.webp) ### Step 2. Configure Custom Connector Follow the steps: 1. Enter a name for the MCP connector. 2. Enter the MCP server URL as `https://mcp-d.docusign.com/mcp` 3. Select **Continue**. 4. Select **Continue anyway**. 5. Under **OAuth client** section, select **Use your own OAuth client**. 6. Enter the generated Integration Key (IK) as **OAuth client ID**. 7. Enter the generated secret key as **OAuth client secret**. 8. Select **Add**. 9. Select **Connect**. ![gif for adding IK and secret key](/_fern-files/_img/49ce3f5d5fedd78a4e6898d781df6745408513a1cd65254635e49c41fe03f095.webp) ### Step 3. Sign in and Grant Access * Sign in to your demo Docusign account. * If you created the app in production environment, sign in to your Docusign production account. * Select **Allow Access**. ![Allow Access](/_fern-files/_img/76ee9b223acb9d5de5959cae59ddd1a0a1d50aad17fef8bfc7256ee3eac722e6.webp) Connecting your Docusign account with Claude requires granting specific permissions to allow the integration to perform tasks on your behalf. These permissions, as shown in the authorization screen, are categorized to ensure Claude can provide comprehensive support across your Docusign account. When you select Allow access, you authorize the Claude application to interact with various Docusign features: * **Document & Envelope Management:** Claude can create and send envelopes, search through existing documents, and obtain signing links to start sessions. * **Workflow Integration:** The integration gains the ability to create and update Web Forms, and access forms within Docusign Rooms or Docusign for Real Estate. * **Account & User Context:** Claude can read your account details, user details, and group lists to understand your users and the categorized groups. * **Specialized API Access:** This includes permissions to make direct calls to the different API and manage search and archive settings for your records. The complete list of MCP tools available in demo and production environments are listed in [MCP tools](/platform/mcp-server#available-tools) section. ### Step 4. Run a test prompt Verify the MCP connection by entering a prompt such as: “List my account information for me”. If successful, Claude will list your Docusign account details with available tools such as `getAllAgreements`, `triggerWorkflow`, `getTabGroups`, and more. **Note**: The wording of AI responses may differ between AI platforms, but the data and results should be the same. ![A screenshot showing the Claude MCP server response to a prompt](/_fern-files/_img/60781003d71c4de0286e2cd3f7775659fe6d4dc3e93010defdc7c94645669e84.webp) ## Docusign Connector Method Follow the instructions in [Connect a Docusign Production Account to Claude](https://support.docusign.com/s/document-item?bundleId=ug3906200f-95c6-4a6b-90b1-f928c85961c6\&topicId=tskaae913c2-c79e-43bd-b32f-f629e5ce358f.html&_LANG=enus) to link your production account through the Claude UI. ## Next steps * Try the Docusign MCP server with [GitHub (Copilot)](/platform/mcp-server/github-copilot) to explore its capabilities in Microsoft Visual Studio Code. * Try the Docusign MCP server with Claude Code [Using Claude Code with Docusign MCP Connector](/platform/mcp-server/anthropic-claude/claude-code) to explore its capabilities in Claude Code. ## Privacy For more details on how Anthropic handles data, privacy, and regional processing, see: * [Where are your servers located? Do you host your models on EU servers?](https://privacy.claude.com/en/articles/7996890-where-are-your-servers-located-do-you-host-your-models-on-eu-servers) * [Data residency (inference geo and workspace geo)](https://platform.claude.com/docs/en/build-with-claude/data-residency) * [Approach to GDPR and related issues](https://privacy.claude.com/en/articles/10023628-what-is-your-approach-to-gdpr-or-related-issues) * [Anthropic Trust Center](https://trust.anthropic.com/) > Learn how to configure Docusign MCP server in Anthropic (Claude). ## Docs - [Using Claude Code with Docusign MCP Connector](https://developers.docusign.com/platform/mcp-server/anthropic-claude/claude-code.md): Learn how to configure Docusign MCP server in Claude Code.