E-signature MCP servers compared (November 2026)
An MCP server lets an AI agent such as Claude, ChatGPT or Cursor use a service directly: the agent sees a list of tools it can call, like "create envelope" or "send reminder", and calls them when you ask. For e-signatures, that means you can say "send this contractor agreement to Jane and remind her on Friday", and the agent does the rest.
A year ago almost no e-signature provider had one. Now most of the big names do, and they differ a lot in what an agent can actually get done. We build md2sign, which has its own MCP server, so we have an obvious interest. We've tried to keep this fair by using only what each vendor's own documentation says, as of 14 November 2026, and linking to it.
What an e-signature MCP server needs to do
An agent sending contracts needs to be able to do more than call a "send" tool. In practice it needs to:
- Send a document it wrote, not only a template someone built in a dashboard beforehand. Agents are good at drafting; a server that only sends pre-built templates throws that away.
- Connect without a developer: remote hosting and OAuth sign-in mean you paste a URL into your AI app and approve access. A local server means installing Node or Python and managing an API key.
- Follow up: check who has signed, send reminders, cancel a request that went out wrong.
- Hand back the result: the signed PDF and the audit trail, so the agent can file them.
- Handle the details real agreements need: signing order, and fields the signer fills in, such as a start date.
The comparison
✓ means the vendor's docs say it's supported. ✕ means they say it isn't. – means their docs don't say either way.
| Provider | Hosting | Sign-in | Sends documents the agent wrote | Templates | Signing order | Signed PDF back | Cheapest plan that can send by API |
|---|---|---|---|---|---|---|---|
| md2sign | Remote | OAuth or API key | ✓ markdown or Word | ✓ (Pro) | ✓ (Pro) | ✓ | $7.50/mo, 50 signature requests |
| DocuSign | Remote | OAuth | ✓ (upload in Claude and ChatGPT) | ✓ | – | – | API Starter, $75/mo, 40 envelopes |
| Dropbox Sign | Remote, via Dropbox | Dropbox account | ✓ | ✕ | ✕ | ✓ | API Essentials, $900/yr, 50 requests/mo |
| PandaDoc | Remote | OAuth | – | ✓ | – | – | API Developer, $40/mo, 40 documents |
| BoldSign | Remote (US, EU, CA, AU) | API key or OAuth | ✕ templates only | ✓ | – | – | $30/mo, 40 envelopes |
| SignWell | Local (npm) | API key | ✓ | ✓ | ✓ | ✓ | Pay per document, from $0.20 |
| Zoho Sign | Remote, via Zoho MCP | OAuth | ✓ | ✓ | – | ✓ | Enterprise or API plan, plus Zoho MCP |
| SignNow | Remote or self-hosted | – | ✓ | ✓ | ✓ | ✓ | – |
| Signbee | Local (npx) | API key | ✓ markdown or PDF | ✕ | – | ✕ | $9/mo, 100 documents |
| DocuSeal | Self-hosted | Bearer token | ✓ via a new template | ✓ | – | ✕ | – |
We found no official MCP server for Adobe Acrobat Sign or Yousign, only third-party wrappers. Documenso's official TypeScript SDK can run as a local MCP server, but its own README describes the v2 API and SDKs as beta.
Provider by provider
DocuSign
DocuSign's MCP server is the most complete of the incumbents. DocuSign announced it would open it to every AI agent on 30 September 2026, and its developer blog now calls it generally available. It's hosted, uses OAuth, and has around 40 tools: creating envelopes (including from up to ten uploaded documents in Claude and ChatGPT), templates, recipient status, reminders, and voiding. Workflow and contract-management tools need a separate IAM subscription, and DocuSign says the tools available depend on your plan.
The catch is cost: DocuSign's cheapest API plan, API Starter, is $75 a month billed monthly for 40 envelopes. Its docs also don't list a tool for downloading the signed PDF.
Dropbox Sign
Dropbox Sign works through Dropbox's remote MCP server, so you connect a Dropbox account (a free one is fine) linked to your Dropbox Sign account. It can send documents, check status, remind, cancel, and download signed copies with their audit trails. Dropbox's help page is clear about its limits: no account templates, advanced signer fields, signing order or branding.
PandaDoc
PandaDoc hosts its server at mcp.pandadoc.com with OAuth. It's built around templates: creating and sending documents from them, tracking status, reminders and search. PandaDoc doesn't publish a full tool list, so we couldn't confirm sending a document the agent wrote from scratch. Its free API plan includes 5 documents a month with 2 recipients each.
BoldSign
BoldSign is hosted in four regions, including Australia, which matters if your data has to stay local. Its MCP server can only send documents from templates you've already set up, so the agent can't send a contract it has just drafted.
SignWell, Zoho Sign and SignNow
All three cover the full loop: sending documents or templates, signing order (SignWell and SignNow), status, reminders and the signed PDF. SignWell runs locally from npm with an API key. Zoho Sign's tools are generated through Zoho MCP, an admin has to switch them on, and sending needs an Enterprise or API plan plus a Zoho MCP subscription. SignNow can be hosted by SignNow or self-hosted from its open-source server.
Signbee
Signbee is the closest to md2sign in spirit: it turns markdown into a PDF and sends it for signature, and it's cheap at $9 a month for 100 documents. Its MCP server is small, though: two tools, both for sending. Checking status or getting the signed PDF back means using its REST API instead, and it runs locally with an API key.
md2sign
We built md2sign for agents first. The server is remote at https://md2sign.com/mcp, and you can connect it three ways: OAuth sign-in from claude.ai, Claude Desktop or any OAuth-capable client; an API key; or no account at all, in which case the agent can validate and preview documents and create an account for you.
Agents write contracts in markdown, with a line like [[signature: Jane Citizen <[email protected]>]] for each signer, or import a Word document. The 24 tools cover the whole loop: validate, preview, email yourself a free test copy, send, remind, void, check progress, and download the signed PDF and audit trail. Pro adds versioned templates, fields signers fill in, signing in order, your logo and webhooks to your CRM.
One difference to know when comparing prices: md2sign counts a signature request per signer, where most others count per envelope. A two-signer contract uses two of Starter's 50 requests, which works out to about $0.30 a contract.
Which one should you use?
- You already pay for DocuSign or Zoho Sign: use their MCP server. It's the least disruption, and both are capable.
- You want templates only, hosted in Australia: BoldSign.
- You want your agent to draft and send its own contracts, cheaply, without installing anything: that's what md2sign is for.
Connect md2sign to Claude
In claude.ai or Claude Desktop, go to Settings → Connectors → Add custom connector and enter https://md2sign.com/mcp/oauth. In Claude Code:
claude mcp add --transport http md2sign https://md2sign.com/mcp/oauth
Then run /mcp to sign in. Your first document is free, for up to 5 signers. The MCP setup page has instructions for other clients and the full tool list.
Sources
Checked on 14 November 2026. Tell us if anything here has changed and we'll update it.
- DocuSign: MCP server docs, availability announcement, API pricing
- Dropbox Sign: MCP help page, API pricing
- PandaDoc: MCP docs, API pricing
- BoldSign: MCP docs, API pricing
- SignWell: MCP page
- Zoho Sign: MCP help article
- SignNow: MCP docs
- Signbee: signb.ee
- DocuSeal: MCP guide
- Documenso: TypeScript SDK