Connect DocuSign to Claude Code

Let Claude prepare envelopes and send them for signature in DocuSign. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect DocuSign to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect DocuSign, you add a DocuSign MCP server: a small hosted service that exposes DocuSign's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own DocuSign account. No API keys pasted into config files.

claude mcp add --transport http docusign https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in DocuSign once connected?

Full read-write DocuSign access lets Claude build an envelope from a template, add recipients and signing order, place signature and date fields, and send it for signature once you approve. The contract prep that used to mean clicking through the DocuSign console happens where the request already started.

Create an envelope from a template and populate its fields
Add recipients and set a signing order on an envelope
Place signature, initial, and date fields for each signer
Send a prepared envelope for signature after you approve it
Send a reminder to a recipient who has not yet signed
Void an envelope that was sent in error, with your confirmation

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same DocuSign access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the DocuSign API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when DocuSign changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build DocuSign connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same DocuSign connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own DocuSign account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on DocuSign's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to DocuSign?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the DocuSign account it signs in with. Revoking access is one click in DocuSign.

More on the DocuSign connector

DocuSign connector for claude.ai PandaDoc + Claude Code Dropbox Sign + Claude Code Adobe Acrobat Sign + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us