Docusign
by Docusign
Query agreements, run Workflow Builder workflows and create envelopes from an AI agent. Anthropic lists 20 tools; Docusign documents 22 available in production, including two that email recipients. OAuth with three coarse scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Docusign via MCP
https://mcp.docusign.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Docusign Tools & Capabilities (20)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- It is Open Beta, and Docusign disclaims warranty. Docusign's beta notice states the server is provided "as is" and "as available" without warranty, that behaviour may change, and that access to certain capabilities is under limited availability.
- Docusign asks for a human in the loop. Its beta notice says users "should have a 'human in-the-loop' to confirm tools and accuracy and appropriateness of AI output", and warns that fully automated agents are more vulnerable to prompt injection. Given that
createEnvelopecan email a signer, we would treat that as a requirement rather than advice. - No scope separates reading from sending. All envelope tools sit behind the single
signaturescope. There is no consent-time way to grant status checks without granting sends and voids. - Anthropic's tool list under-reports the outbound surface.
updateEnvelopeRecipientsandsendReminderare documented as production-available and are absent from the directory listing. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request. Parameter behaviour on this page is sourced from Docusign's REST reference.
- You must register your own OAuth app. Only the Confidential Authorization Code Grant is supported, so dynamic client registration is unavailable and connecting is a manual, admin-level task.
- Production covers a subset. Docusign states production connectors "currently support only seven API groups", and marks Connected Fields, Data Verification,
generateAccessToken,searchDocusignDocsandsuggestBestPracticesas demo-only. - A single account context. Claude connects to one Docusign environment at a time; querying the other requires reconnecting.
- Rate limits are enforced but undocumented here. The endpoint returned
ratelimit-limit: 800headers to an unauthenticated request on 2026-08-22. Docusign publishes no MCP-specific limit that we found. - Docusign's own published documentation link is dead. The
documentationURL in Anthropic's directory entry — and theresource_documentationfield in Docusign's own RFC 9728 descriptor — both point atdevelopers.docusign.com/tools/mcp-server/, which returned 404 on 2026-08-22. The live page is at/platform/mcp-server/.
Frequently asked questions
Yes. Docusign's eSignature API documents that createEnvelope sends the envelope to recipients when status is set to sent, and saves a draft when status is created or left unset. Sending is therefore a parameter value, not a separate tool name. Docusign's own Claude consent screen states the integration can create and send envelopes.
It can void one. Docusign describes updateEnvelope as covering voiding, sending draft and email changes, and the underlying REST operation is summarised as send, void, or modify a draft envelope, plus purge documents from a completed envelope. Voiding makes an envelope permanently invalid to recipients, so treat it as irreversible.
Anthropic lists 20, and Docusign documents 22 as available in production out of 35 total. The two production tools absent from the directory listing are updateEnvelopeRecipients and sendReminder. Both email real people, so the directory listing under-reports precisely the surface a reader most needs to know about.
Three scopes, and none of them separates reading from sending. The server's RFC 9728 descriptor advertises signature, aow_manage and adm_store_unified_repo_read. Docusign defines signature as required to call most eSignature REST API endpoints, so granting envelope reads also grants envelope creation, sending and voiding.
Yes. Docusign supports only the Confidential Authorization Code Grant, so you create an app in the Docusign Apps and Keys page, copy the Integration Key and a client secret, and register two redirect URIs pointing at claude.ai and claude.com. Claude cannot register itself automatically against this server.
Docusign labels it Open Beta and provides it as-is without warranty. Its beta notice states the feature may change, that access to certain capabilities is under limited availability, and that users should keep a human in the loop to confirm tools and the accuracy of AI output. Both developer and production accounts are supported.
Yes, in its own beta notice. Docusign states that running agents in a fully automated fashion increases vulnerability to exposure via prompt-injection attacks, and advises connecting with least-privileged accounts. That matters here because envelope and agreement text is written by counterparties, which makes it untrusted input reaching an agent that can send.
Seven groups, of which four reach production. Docusign documents eSignature, Workflow Builder and Agreement Manager tools as available in production, plus one authentication tool. Connected Fields, Data Verification, documentation search and access-token generation are demo-only. Docusign states production connectors currently support only seven API groups.
Sources
- Docusign MCP server documentation, "Build with the Docusign MCP Server (Beta)" (retrieved 2026-08-22). Content is client-rendered; the endpoint tables were read from the page's own
page-data.json. · retrieved 2026-08-22 - Docusign MCP setup for Anthropic Claude (retrieved 2026-08-22) · retrieved 2026-08-22
- Docusign MCP setup for Claude Code (retrieved 2026-08-22) · retrieved 2026-08-22
- Docusign eSignature REST API, Envelopes: create (retrieved 2026-08-22) · retrieved 2026-08-22
- Docusign eSignature REST API, Envelopes: update (retrieved 2026-08-22) · retrieved 2026-08-22
- Docusign eSignature REST API, EnvelopeRecipients create · update · delete — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Docusign authentication scopes reference (retrieved 2026-08-22) · retrieved 2026-08-22
- Live auth posture check: an anonymous initialize returned 403 and a bearer-token request returned 401 with
www-authenticate: Bearer realm="https://mcp.docusign.com/mcp"; RFC 9728 metadata athttps://mcp.docusign.com/.well-known/oauth-protected-resourceand authorization server metadata athttps://mcp.docusign.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
developers.docusign.com/robots.txtallows the documentation paths fetched here (retrieved 2026-08-22) · retrieved 2026-08-22- Docusign support portal, as listed in Anthropic's directory entry (returned a 301 to our client on 2026-08-22 and would not resolve further; not used as a source) · Privacy (retrieved 2026-08-22) · retrieved 2026-08-22
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Docusign
- Tools
- 20
- Domain
- mcp.docusign.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.