DocuSign MCP Server
Create, send, and track agreements and query signature status through Docusign's Intelligent Agreement Management platform, connecting via OAuth with no API key setup.
- Maintained by
- Docusign
- Last checked
In open beta. Developer (demo) accounts connect to https://mcp-d.docusign.com/mcp with OAuth.
Frequently asked questions
What is the DocuSign MCP server?
It is a Model Context Protocol (MCP) server — a small piece of software that gives AI assistants like Claude a secure, governed connection to DocuSign. Create, send, and track agreements and query signature status through Docusign's Intelligent Agreement Management platform, connecting via OAuth with no API key setup.
Is there an official DocuSign MCP server?
Yes. The DocuSign MCP server is an official integration, maintained by the vendor or the Model Context Protocol project, which makes it the safest default for business use. It is maintained by Docusign.
What can an AI assistant actually do with DocuSign?
Through this server an assistant can work with send agreements, envelope tracking, agreement data, workflows — reading from and acting on DocuSign directly instead of you copy-pasting between windows. What you allow it to do is controlled by the permissions you grant.
How do I set this up for my business?
Technically-minded teams can connect an MCP server themselves; our plain-English guide to MCP explains how the pieces fit. Once it is running against real systems, the question becomes what catches it when it acts wrongly, which is what Crox's Safety Diagnostic looks at.
New to MCP? Start with our plain-English guide to the Model Context Protocol or see how to connect AI to your business tools without writing code .
Already running this in production?
An agent with a live connection to your tools is a model that can act. Crox looks at what catches it when it acts wrongly: the layers around it, who can stop it, and where a near miss gets reported. Two days, one team, one model.