How to
How to connect Claude to DocuSign
DocuSign ships an official Claude connector in Open Beta, and it can already create and send envelopes from your templates. The question is what happens when a contract does not fit a template, or you want every send behind your own approval gate.
Connect Claude to DocuSign either with the official connector, an Open Beta that already creates and sends envelopes from your existing templates, or with a custom MCP connector when you need more. A custom build adds custom field placement, non-template workflows, multi-account control, and per-action approval gating, authenticated as your own DocuSign account.
Key takeaways
- DocuSign has an official Claude connector in Open Beta that can create and send envelopes for signature today, working from your existing templates.
- Direct file uploads are the documented limit of the official path, not sending; the other gaps are custom field placement, non-template workflows, and multi-account control.
- A custom connector lets Claude build an envelope from a template, add recipients and signing order, place signature, initial, and date fields, and send reminders to unsigned recipients.
- Send and void are separate, gated actions: Claude stages the envelope, and nothing goes out or gets voided until you confirm.
Does DocuSign have an official Claude connector?
Yes. DocuSign ships an official Claude connector in Open Beta, and it can already create and send envelopes for signature, working from your existing templates. Direct file uploads are the documented limit, not sending. The gaps are custom field placement, non-template workflows, multi-account control, and per-action approval gating.
Start with the honest version: if your agreements all run through well-built templates and you are comfortable with the beta's defaults, the official connector may carry your signing workflow today. Connect it and try it first.
The friction shows up off the template path. A one-off contract that needs fields placed by hand, a document that is not in your template library, a team that signs from multiple DocuSign accounts, or a policy that every send must pause for review: those are the cases the template path leaves out, and the gap a custom DocuSign connector is built for.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom DocuSign connector for Claude?
A custom DocuSign connector is built for you as a small MCP server that authenticates with OAuth 2.0 using the narrowest scopes the work needs. Read tools like envelope lookup are separated from write tools like create envelope, place fields, and send, and send and void always require your confirmation.
The path from request to working connector:
- 1Describe the DocuSign work Claude should handle, including your templates, signing workflows, and any accounts that need coverage.
- 2We build a small MCP server with read tools (look up envelope, list recipients) separated from write tools (create envelope, place fields, send).
- 3You authenticate through OAuth 2.0 as your own DocuSign account, so Claude inherits your existing permissions and nothing more.
- 4Claude starts preparing envelopes in conversation, and outbound or destructive actions like send and void run only after you confirm them.
Access is revocable at any time, and the connector never holds broader scopes than the work requires.
What can Claude do in DocuSign with write access?
With full read-write access, Claude creates an envelope from a template and populates its fields, adds recipients and sets a signing order, places signature, initial, and date fields for each signer, sends the prepared envelope once you approve, reminds recipients who have not signed, and voids a mistaken envelope with your confirmation.
The tool set maps to the contract prep most teams click through the console to do:
- 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.
The result is that contract prep happens where the request already started: Claude assembles and stages the envelope in the same conversation that produced the deal terms, and you review before it goes out.
Will Claude send or void a DocuSign envelope without asking?
No. Sending an envelope and voiding one are separate, gated write actions. Claude can prepare the envelope, populate fields, and stage the recipients, but it only sends or voids after you approve that step. You decide which actions run automatically and which require explicit confirmation first.
Signature requests are a special class of write: once an envelope reaches a counterparty's inbox, there is no quiet undo. That is why the gate sits exactly on send and void rather than on the whole connector. Field placement, recipient staging, and reminders can flow freely, and the irreversible steps always pause.
Claude only has your access
The connector authenticates as your account through OAuth and inherits your existing permissions. If you cannot send from a given account or see a particular envelope, neither can Claude, and you can revoke the connection at any time.
When is the official DocuSign connector enough, and when is it not?
The official connector is enough when your signing runs through existing templates and the beta's defaults fit your process. It stops being enough when you need custom field placement, non-template documents, coverage across multiple accounts, or your own gate on every send. Those are custom-connector territory.
A quick self-test: look at your last ten envelopes. If every one came from a template unchanged, connect the official connector today. If any needed fields placed by hand, came from a document outside your template library, or went out under a review-before-send policy, the template path will not carry them, and a purpose-built connector will.