How to Connect DocuSign to AI Agents with the MCP Server

DocuSign processes over one billion agreements annually. Most developers who integrate with DocuSign still write custom REST API code to handle envelope creation, recipient routing, and status polling. The DocuSign MCP server, currently in beta, wraps these capabilities into the Model Context Protocol so AI agents can interact with agreements through natural language instead of raw API calls.

The MCP server sits at https://mcp-d.docusign.com/mcp and exposes DocuSign's Intelligent Agreement Management (IAM) platform to any MCP-compatible client. That includes Claude Desktop, Claude Code, ChatGPT, GitHub Copilot, and custom agent frameworks.

What agents can do through the DocuSign MCP server:

• Create and send envelopes for signature, either from scratch or from templates
• Check envelope status, including whether documents have been viewed, signed, declined, or voided
• Query agreement metadata and key dates through Navigator
• Trigger Maestro workflows for multi-step approval processes
• Retrieve agreement context, clauses, and AI-powered insights
• Manage bulk send lists and add recipients to existing lists
• Add documents and users to DocuSign workspaces

The server uses the same underlying technology that powers DocuSign's ChatGPT integration. Because it implements the open MCP standard, any agent that speaks MCP can connect without custom adapter code. You describe what you want in plain language, and the agent translates that into the correct API calls.

There are two setup paths depending on whether you are working with a developer sandbox or a production DocuSign account.

Developer Account Setup

This path works immediately without beta approval. You register your own integration key and point your MCP client at the server URL.

1. Log into your DocuSign developer account and go to the Apps and Keys page
2. Create a new Integration Key (IK) and note the Secret Key
3. Add these redirect URIs to your integration key:
   • https://claude.ai/api/mcp/auth_callback
   • https://claude.com/api/mcp/auth_callback
4. In Claude Desktop or claude.ai, go to Settings, then Connectors, then Add Custom Connector
5. Enter a name for the connector, set the Remote MCP server URL to https://mcp-d.docusign.com/mcp, and paste your Client ID (the Integration Key) and Client Secret
6. Click Add, then Connect
7. Authenticate with your DocuSign credentials and grant consent

After authorization, Claude can immediately start working with envelopes and agreements in your sandbox.

Production Account Setup

Production access requires enrollment in the DocuSign MCP beta program. Submit the request form on the DocuSign developer portal, and once approved:

1. Open Claude Desktop or claude.ai and navigate to Settings, then Connectors, then Browse Connectors
2. Search for DocuSign and select Connect
3. Authenticate with your production DocuSign credentials
4. Grant the requested permissions

The production connector is pre-registered, so you skip the Integration Key setup. Your permission scopes determine which agreement data and actions the AI agent can access.

Requirements

• A DocuSign account (developer or production)
• Claude Pro subscription or higher for claude.ai, or Claude Desktop installed
• For other MCP clients: any application that supports remote MCP server connections

Once connected, the real value comes from combining DocuSign actions into multi-step workflows. Here are concrete examples that go beyond simple "send an envelope" demos.

Agreement Status Dashboard

Ask your agent to pull a summary of all pending agreements for a specific client. A prompt like "List all agreements for Acme Corp that are Sent but not Signed and summarize total value" returns structured data from Navigator without writing any query code. The agent handles the API pagination and data aggregation.

Template-Based Sending

If your team uses standardized contracts, the agent can create envelopes directly from DocuSign templates. "Using the Employee Code of Conduct template, send a new document for signature to jane@acme.com" creates the envelope, populates the recipient, and sends it in one step. Set status to "sent" for immediate delivery, or "created" to save as a draft for review.

Workflow Automation with Maestro

DocuSign

Maestro handles complex approval chains, conditional routing, and multi-party signing flows. Through MCP, agents can trigger these workflows directly. "Start an NDA workflow using DocuSign Maestro with a reminder 30 days prior to expiration" kicks off the defined workflow without navigating the Maestro UI.

Agreement Intelligence

Navigator uses AI to extract structured data from your agreement repository. Through the MCP server, agents can answer questions like "Do I have an active NDA in place with Fontara?" by querying Navigator's indexed agreement data. This turns your agreement archive into a searchable knowledge base that agents can reason over.

Signing Status Monitoring

Build reactive workflows by having agents check envelope status on a schedule. When a document moves from "sent" to "completed," the agent can trigger downstream actions: notify a Slack channel, update a CRM record, or move the signed document into a shared workspace for archival.

Store and search your signed agreements automatically

Fastio gives AI agents a persistent workspace for signed documents, with built-in search, permissions, and audit trails. generous storage, no credit card required.

Start 14-Day Trial

The official DocuSign MCP server is the most direct path, but it is not the only option. Depending on your stack and requirements, other approaches may fit better.

Zapier MCP

Zapier exposes

DocuSign actions through its own MCP endpoint. This bundles DocuSign with access to over 8,000 other apps, so you can chain signing workflows with CRM updates, Slack notifications, or database writes in a single agent conversation. Each MCP tool call consumes two tasks from your Zapier plan quota. Setup takes minutes through the Zapier MCP dashboard, and it works with Claude, Cursor, and other MCP clients.

Composio

Composio provides a DocuSign MCP integration that works with Claude Code, Claude Agent SDK, and other agent frameworks. It handles OAuth token management and exposes DocuSign tools through a standardized interface. Composio is useful when you need to connect multiple SaaS tools to the same agent without managing individual MCP servers.

CData Connect AI

CData offers a read-only

DocuSign MCP server that connects through JDBC drivers. This is oriented toward data access rather than action execution. If your use case is querying DocuSign data (pulling envelope metadata, listing recipients, reporting on signing activity) rather than sending documents, CData provides a straightforward path.

Luther Systems MCP Server

The open-source mcp-server-docusign from Luther Systems uses JWT server-to-server authentication instead of OAuth. This is a good fit for backend agent systems that run without user interaction, where you want a service account to manage envelopes programmatically.

Direct REST API

For maximum control, you can skip MCP entirely and build custom tool definitions that call the DocuSign eSignature REST API. This requires more code but gives you fine-grained control over error handling, retries, and payload construction. Most teams start here and migrate to MCP once their workflows stabilize.

DocuSign handles the signing workflow, but signed documents need a home after execution. Dropping completed agreements into a local folder or email attachment chain creates the same disorganization that e-signatures were supposed to fix.

Fastio provides intelligent workspaces where agents can store, organize, and query signed agreements alongside related project files. When your agent detects a completed envelope through DocuSign MCP, it can use the Fastio MCP server to upload the signed document into the right workspace, set permissions, and notify the relevant team.

Why this pairing works:

• Fastio's Intelligence Mode auto-indexes uploaded documents for semantic search. Once a signed contract lands in a workspace, team members can ask questions about its terms through AI chat, with citations pointing back to specific clauses
• Granular permissions let you control who sees what. An agent can upload a signed NDA to a workspace where only legal and the counterparty have access
• Audit trails track every file action. When compliance asks who accessed an agreement and when, the log is already there
• Ownership transfer lets an agent build and populate a workspace, then hand it to a human project manager. The agent retains admin access for ongoing automation while the human owns the client relationship

The Fastio MCP server exposes workspace, storage, AI, and workflow operations through Streamable HTTP at /mcp. Agents that already use DocuSign MCP can add Fastio as a second MCP connection and orchestrate the full lifecycle: draft, send, sign, store, and search.

The Business Trial includes 50GB of storage, included credits, and five workspaces, with no credit card required. That is enough to handle agreement storage for most small teams. See the storage for agents page for setup details.

The DocuSign MCP server is still in beta, and there are practical constraints worth knowing before you build production workflows around it.

Beta availability. Production account access requires enrollment in the beta program. Developer sandbox access works immediately, but sandbox data does not reflect your real agreements. Plan for a transition period when moving from sandbox to production.

Permission scoping. The OAuth consent screen determines what your agent can access. If you grant read-only scopes, the agent cannot send envelopes. Review the permission request carefully during setup, and use the principle of least privilege. An agent that only needs to check signing status should not have envelope creation permissions.

Response variability. DocuSign's documentation notes that AI responses may vary by model, even when the underlying data is consistent. The same prompt might return differently formatted summaries depending on which LLM you use as your MCP client. Build your workflows to handle structured data from DocuSign tools rather than relying on specific response formatting.

Latency. MCP adds a network hop between your agent and the DocuSign API. For real-time automation where milliseconds matter, direct API integration may still be the better choice. For conversational workflows where a human is in the loop, MCP latency is not noticeable.

Tool coverage. Not all IAM tools are available in every environment. Some capabilities, like Navigator queries, depend on your DocuSign plan tier. Check which tools are exposed in your specific setup before designing workflows that depend on them.

Sensitive workflows. Sending agreements for signature is a consequential action. Consider building confirmation steps into your agent workflows, where the agent prepares the envelope and shows a summary before the human approves the send. Most MCP clients support this pattern through tool confirmation prompts.