Docusign MCP Server

The Docusign MCP Server is an official, provider-hosted Model Context Protocol server that exposes Docusign's Intelligent Agreement Management (IAM) platform to AI agents. It is currently in beta and lets clients like Claude, Cursor, VS Code, and GitHub Copilot interact with eSignature envelopes, templates, Maestro workflows, and Navigator agreement data through natural language instead of raw REST API calls.

The server covers four primary surface areas: eSignature (create, send, update, and track envelopes, manage recipients, send reminders, list templates), Maestro (list workflows, inspect trigger requirements, start, pause, resume, and cancel workflow instances), Navigator (list and retrieve metadata for stored agreements with filters by counterparty, type, and date), and account/user management (get current user info, account details, and list users). Authentication is OAuth 2.0 using a Docusign Integration Key and Secret Key, with Claude's MCP auth callback as the redirect URI.

Because the server is hosted directly by Docusign, there is no self-hosted code to deploy. Users register an integration in the Docusign developer console, then add the remote MCP URL as a custom connector in their AI client. Production access requires beta approval from Docusign; developer accounts can use the developer endpoint immediately.

Tools

Prerequisites

• A Docusign account (developer account for beta, production requires beta approval)
• An Integration Key (Client ID) and Secret Key (Client Secret) from the Docusign Apps and Keys page
• An MCP-capable client: Claude (Pro or above), Cursor, VS Code, or GitHub Copilot

Create a Docusign integration

1. Sign in to your Docusign developer account and open Settings then Apps and Keys.
2. Add a new app, copy the Integration Key, and generate a Secret Key.
3. Add the following redirect URIs:
   • https://claude.ai/api/mcp/auth_callback
   • https://claude.com/api/mcp/auth_callback

Claude Desktop (custom connector)

In Claude Desktop go to Settings, then Connectors, then Add custom connector and fill in:

• Name: Docusign
• Remote MCP server URL: https://mcp-d.docusign.com/mcp
• Client ID: your Integration Key
• Client Secret: your Secret Key

For clients that read a JSON config, use:

{
  "mcpServers": {
    "docusign": {
      "url": "https://mcp-d.docusign.com/mcp",
      "transport": "http",
      "auth": {
        "type": "oauth2",
        "client_id": "YOUR_INTEGRATION_KEY",
        "client_secret": "YOUR_SECRET_KEY"
      }
    }
  }
}

Production accounts that have been approved for beta can connect via the Claude Connectors Directory rather than entering the URL manually.

Notes

• The server is in beta. Behavior and tool surface may change.
• Use the developer endpoint (mcp-d.docusign.com) for testing against demo Docusign accounts.

• Draft a contract, create an envelope from a Docusign template, and send it to a counterparty without leaving the AI chat
• Check the status of pending envelopes and automatically send reminders to signers who have not yet completed their tabs
• Query Navigator for all NDAs with a given counterparty signed in the last 12 months and summarize key clauses
• Kick off a Maestro approval workflow when an AI agent determines a deal meets predefined criteria, then monitor the instance to completion
• Pause new instances of a Maestro workflow during a release freeze and resume it afterward, all from a single agent prompt

• "Send the MSA template to jane@acme.com and bob@acme.com, then notify me when both have signed."
• "List every envelope still waiting on a signature for more than 7 days and send each signer a reminder."
• "Find all agreements in Navigator with Acme Corp expiring in the next 90 days and summarize their renewal terms."
• "Trigger the 'New Vendor Onboarding' Maestro workflow with vendor name 'Globex' and contact 'lee@globex.com'."
• "Cancel the running Maestro instance with ID abc123 and tell me which step it was on."

• Official, Docusign-hosted server with no self-hosting required
• Broad tool coverage across eSignature, Maestro workflows, and Navigator agreement intelligence
• Standard OAuth 2.0 flow using existing Docusign Integration Keys, so permissions follow normal Docusign governance
• Works with major MCP clients including Claude, Cursor, VS Code, and GitHub Copilot

• Currently in beta, so the tool surface and stability can change without notice
• Production deployment requires Docusign beta approval; only developer accounts are open by default
• No public source repository, so behavior cannot be inspected or extended by the user

• luthersystems/mcp-server-docusign: community FastMCP server using JWT server-to-server auth for the eSignature API
• thisdot/docusign-navigator-mcp: community MCP server focused on Navigator agreement queries
• CDataSoftware/docusign-mcp-server-by-cdata: read-only MCP server backed by CData JDBC drivers for Docusign data