DocuSign documentation
Research date: 2026-08-24
Documentation coverage: not-retrieved.
Reference index, not a mirror of complete vendor documentation. Retrieved pages do not prove the MCP works.
What it does
E-signature and Intelligent Agreement Management (IAM) platform; the CLM/AI side covered here is agreement creation, status tracking, and AI-assisted querying/analysis of agreement data via MCP, distinct from plain e-signature.
Access and connection
MCP support: official
Access requirements: paid, tiered by envelope volume. DocuSign's Developer API plans run Starter ($50/mo or $600/yr, 40 envelopes/mo) through Intermediate ($300/mo, 100 envelopes/mo) to Advanced ($480/mo, unlocks Bulk Send/PowerForms/Connect webhooks) and Enterprise (custom); a free developer sandbox account exists for prototyping but is explicitly not production-usable. The MCP Server itself is described as available to both developer and production accounts in Open Beta with "no intake form or approval required," which is a notably low-friction access point relative to the metered envelope API underneath it.
Authentication: OAuth - Streamable HTTP transport; first connection opens a browser window to sign in and authorize, then reuses credentials.
Research checked: 2026-08-24
These details come from the catalog research. Check the vendor sources below for current setup instructions. They do not establish that a connection or tool call was tested.
Sources
- https://developers.docusign.com/platform/mcp-server/
- https://mcpservers.org/remote-mcp-servers/docusign
- https://www.pulsemcp.com/servers/docusign
- https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide
- https://ecom.docusign.com/plans-and-pricing/developer
- https://mcp.docusign.com/mcp
- https://community.docusign.com/general-74/building-with-ai-just-got-easier-introducing-the-docusign-mcp-server-25912