Docusign

Query agreements, run Workflow Builder workflows, create envelopes.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Docusign connector does

The Docusign MCP server connects a Docusign account to Claude, ChatGPT and any MCP-compatible agent. It reads agreements and envelope status, runs Workflow Builder workflows, and creates envelopes that can be sent for signature. Sign-in is OAuth through Docusign's own account server, using an app you register yourself. Docusign labels the server Open Beta.

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.

Docusign tools (20)

  • getUserInfo
  • getAllAgreements
  • getAgreementDetails
  • getWorkflowTriggerRequirements
  • getWorkflowsList
  • triggerWorkflow
  • getWorkflowInstancesList
  • getWorkflowInstance
  • pauseNewWorkflowInstances
  • resumeWorkflow
  • cancelWorkflowInstance
  • getEnvelopes
  • getEnvelope
  • createEnvelope
  • updateEnvelope
  • listRecipients
  • getTemplates
  • getUser
  • getUsers
  • getAccount

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 createEnvelope can 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 signature scope. There is no consent-time way to grant status checks without granting sends and voids.
  • Anthropic's tool list under-reports the outbound surface. updateEnvelopeRecipients and sendReminder are 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, searchDocusignDocs and suggestBestPractices as 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: 800 headers 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 documentation URL in Anthropic's directory entry — and the resource_documentation field in Docusign's own RFC 9728 descriptor — both point at developers.docusign.com/tools/mcp-server/, which returned 404 on 2026-08-22. The live page is at /platform/mcp-server/.

Frequently asked questions

Can the Docusign MCP server actually send an agreement for signature?

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.

Can the connector void or delete a Docusign envelope?

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.

How many tools does the Docusign MCP server have?

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.

What OAuth permissions does the Docusign MCP server request?

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.

Do I need my own Docusign app to connect Claude?

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.

Is the Docusign MCP server production-ready?

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.

Does Docusign warn about prompt injection through this connector?

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.

Which Docusign APIs does the MCP server cover?

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

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Docusign to work.

Connect Docusign once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio