A Developer Guide to Using Claude with the Docusign MCP Connector

Developers building agreement AI workflows need secure access to real agreement data and lifecycle actions. The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities. This guide explains how the integration works, how to set it up, and how to use the connector to build agreement-aware workflows.

Connect AI assistants to Docusign agreement intelligence with MCP

The Model Context Protocol (MCP) is an open standard developed by Anthropic that enables AI assistants to securely connect to external systems. An MCP server provides a standardized interface that allows AI applications to access data and perform actions through integrated tools. 

Claude Connectors Directory lists all the enterprise MCP servers that work with Claude. The Docusign MCP connector is now available in this directory and allows Claude to securely access Docusign IAM and eSignature capabilities through MCP while operating within established authentication and permission boundaries. 

The Docusign MCP Server implements this protocol to expose the core capabilities of Docusign IAM, including agreement data, context, and workflow actions, through a secure and governed interface.

This allows developers to:

• Retrieve agreement context and metadata

• Query agreement status and key dates

• Access clauses and agreement insights

• Trigger workflow actions through IAM tools

• Integrate agreement intelligence into AI-driven workflows

By using MCP, developers can enable agreement-aware automation without building custom API orchestration.

Because the MCP Server implements an open standard, it can be used with multiple AI clients and agent frameworks and is not limited to Claude. 

In this post, we show you how to connect Claude to your Docusign account using MCP. Future posts will show how to build automated agentic workflows using this setup.

Prerequisites

Before getting started, ensure you have:

• A Docusign account (either a production account or a developer account).

• Anthropic Claude account Pro or above.

• Claude Desktop installed on your computer.

Accessing the Docusign MCP Server with Claude

Developers can access the Docusign MCP Server through MCP-compatible AI clients. This guide focuses on Anthropic Claude, where the MCP Connector enables secure access to IAM capabilities.

Two options to connect:

Developer account If you are a developer, you can use a free Docusign developer account and add a custom connector to Claude. 

💡Future tools and features will be deployed to developer accounts early, allowing developers to explore and learn about new capabilities and enhancements before they become available to other customers. 

Production account If you are not a developer, you will have to request access to the beta connector feature using this form. Once access is granted, you will be notified via email and you can then follow the rest of the process below.

Connect using a developer account

1. Go to the Apps and Keys page of your developer 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 (copy its value right away).

6. Add these two URIs in Redirect URIs section:

   • https://claude.ai/api/mcp/auth_callback 

   • https://claude.com/api/mcp/auth_callback

   

7. Open Claude Desktop or sign in at claude.ai.

8. Select Avatar → Settings → Connectors → Add Custom Connector.

   

9. Enter Name, Remote MCP server URL (use https://mcp-d.docusign.com/mcp), Client ID (IK), and Client Secret (Secret Key) you generated in the Apps and Keys page.

10. Select Add.

11. Select Connect.

12. Sign in to your Docusign account.

13. Select Allow Access to grant consent.

Connect using a paid production account 

Note: This option requires approval of our beta program.

On your Claude AI do this:

1. Open Claude Desktop or sign in at claude.ai.

2. Select Avatar → Settings → Connectors → Browse Connectors.

3. Search for Docusign.

4. Select Connect.

5. Sign in to your Docusign account. You will then see this dialog.

6. Select Allow Access to grant consent.

Why use the connector?

• Eliminates integration complexity

• Provides a supported, production-ready setup

• Allows teams to focus on building workflows instead of connection setup

Enable agreement-aware workflows with Claude

Once connected, Claude can use IAM capabilities surfaced through MCP to understand agreement context and support workflow automation.

Developers can enable workflows such as:

• Envelope management: sending and checking status of existing documents

• Workflow routing: trigger Maestro Workflows directly from Claude

• AI powered agreement insights: query status, clauses, and agreements using Navigator

Example prompts

Developers can use natural language prompts to retrieve agreement insights and trigger actions.

Examples:

• “Using the Employee Code of Conduct template, send a new document for signature.”

• “List all agreements for Acme Corp that are Sent but not Signed and summarize the total value.”

• “Do I have an active NDA in place with Fontara?”

• “Start an NDA workflow using Docusign Maestro reminder 30 days prior.”

Enterprise governance, permissions, and security

The Docusign MCP Server surfaces IAM capabilities while the same permissions, access controls, and audit policies continue to be enforced by Docusign.

Actions initiated through Claude or other AI assistants operate within existing governance boundaries. Authentication uses Docusign OAuth credentials, ensuring secure, permission-based access.

This enables developers to extend workflows while maintaining the same security and governance standards they rely on in Docusign.

Constraints and considerations

When designing AI-driven agreement workflows, consider:

• AI responses may vary by model, even when data results are consistent.

• Permission scopes determine what agreement data can be accessed.

• Sensitive workflows may require human review or approval steps.

• Latency may affect real-time automation scenarios.

• Not all IAM tools may be available in every environment.

What is the benefit for developers?

By connecting Claude to Docusign through MCP, developers can build systems that understand agreement context and trigger lifecycle actions. They can also explore Docusign platform capabilities through interactions with Claude, without needing to read extensive documentation.

This approach reduces integration complexity and enables agreement workflows to operate as part of broader business systems. See this experience in action for automating complex agreement workflows:

Beyond Claude: MCP as a reusable AI access layer

While this guide focuses on Claude, the Docusign MCP Server implements the open Model Context Protocol and is not limited to a single AI client.

Developers can extend the same architecture to:

• Other MCP clients in other AI platforms

• Internal enterprise GitHub Copilot

• Agent frameworks and orchestration systems

Next steps

• Explore the Docusign MCP capabilities.

• Submit a request for MCP beta access for your Docusign production account and install the Claude Connector to test agreement queries.

• Join the Community thread to share questions and use cases.