An AI agent that drafts a contract and then dumps it in your inbox is not a signing workflow. Agent-capable e-signature software exposes the envelope lifecycle as tools the model can call: upload, place fields, route, send, poll, download evidence. The signature itself is a separate legal act.
Cipher Projects built SumoSign. We ship its remote MCP at https://mcp.sumosign.app/mcp. This page is a first-hand comparison, not a neutral awards list. We disclose that up front and give every row a best-for line and an honest limit, including ours.
Quick answer
MCP support is table stakes in 2026. The buying question is whether the agent’s credential can complete a signature. On SumoSign it cannot: a scoped ss_live_… key prepares, sends, and tracks; only a human one-time signing token completes. DocuSign is the incumbent with an official remote MCP (https://mcp.docusign.com/mcp), a Claude Connectors Directory listing, and a Grok Bot marketplace plugin. It is still in open beta until the 30 September 2026 general-availability date Docusign announced on 4 September. Cutover: counterparties require DocuSign → stay there. EU qualified signatures → eID Easy. Self-host → DocuSeal. Two-party NDA in one tool call → Signbee. Agent-operated multi-party envelopes with a key that cannot sign, plus Claude custom connector and Grok Bot custom plugin → SumoSign.
Best for: teams wiring Claude, Grok Bot, Cursor, or a custom orchestrator to real envelopes. Honest limit: SumoSign is not in Anthropic’s Connectors Directory yet (submission needs a Claude Team or Enterprise org) and is not in Grok Bot’s in-app marketplace catalog. Custom connectors work today. Vendor facts below are from public docs as of 6 September 2026. Verify live URLs before you ship.
Cipher Projects is an Australian-led AI engineering studio. We compare this category because we run agents against our own signing API in production, not because we implemented DocuSign MCP for a client last week.
Last updated: 6 September 2026.
What does agent-capable e-signature actually mean?
Three different doors get sold as the same feature. They are not.
| Door | What it is | What it is not |
|---|---|---|
| Remote MCP URL | A Streamable HTTP endpoint an agent host can paste. Grok Bot, grok.com Connectors, Claude custom connectors, Cursor HTTP MCP, ChatGPT custom connectors. | A directory listing. Anyone with the URL can add it if the client supports custom connectors. |
| Local stdio package | npx … on the laptop. Claude Desktop, Cursor, Windsurf, Claude Code. |
A cloud bot. Grok Bot and Claude on the web cannot spawn your npx process. |
| Catalog listing | Claude Connectors Directory, Grok Bot Settings → Plugins marketplace, Anthropic Cowork connectors. | Proof the protocol works. It is distribution. Anthropic’s directory submission portal requires a Team or Enterprise org. |
Zapier, Make, or a REST API wrapped in a prompt is not MCP. The agent can still send envelopes that way. You lose tool discovery, typed schemas, and a single config that travels across Claude, Cursor, and Grok. If the buying question is “can my agent operate this,” REST plus llms.txt is enough. If the question is “can Claude or Grok Bot connect without me writing a client,” you need a remote MCP URL.
The legal cutover sits under all three doors. US ESIGN (15 U.S.C. §7001(h)) and UETA already recognise contracts formed by electronic agents, with the act attributed to whoever deployed the agent. That is not a licence for the same API key to impersonate a signer. Prompt injection against a send-and-sign tool is a forged contract. The architecture we ship, and the one we recommend you demand, is two credentials: the agent authenticates; the human signs.
Which e-signature tools have an official MCP server in 2026?
The ranking listicles do not even agree on the set. Signvoy’s July 2026 table covers Signvoy, Docusign, PandaDoc, SignNow, BoldSign, and SignWell. Signbee’s September 2026 roundup lists Signbee, DocuSeal, eID Easy, DocsAutomator, SignNow, Signaturit, Papersign, and Autenti. Neither includes SumoSign. ChatForest tracks the vendor-official camp and still misses the agent-native row. That is the missing source this page fills.
Adobe Acrobat Sign, Dropbox Sign, Zoho Sign, Yousign, Oneflow, and GetAccept still had no official MCP server as of Signvoy’s 29 July 2026 check. Dropbox Sign reaches Grok Build through Composio’s gateway, which is middleware, not a vendor server. Treat community wrappers as a last resort: they rarely split create from send.
| Platform | MCP hosting | Claude | Grok Bot | Agent can complete a signature? | Starting public price |
|---|---|---|---|---|---|
| SumoSign | Remote https://mcp.sumosign.app/mcp + stdio @sumosign/mcp |
Custom connector (OAuth). Not in Connectors Directory yet. | Custom plugin, bearer header. Not in the in-app marketplace catalog. | No. Key cannot complete. Human one-time token only. | $79/mo, 100 envelopes, API+MCP included. 30-day trial, 25 envelopes, no card. |
| Docusign | Remote https://mcp.docusign.com/mcp (demo mcp-d.docusign.com) |
Connectors Directory (beta, English). Cowork partnership 24 Feb 2026. | In-app marketplace plugin via official remote MCP (beta). | Not documented as a hard API block. Beta terms tell you to keep a human in the loop. | Per-seat SaaS; API and IAM often plan-gated. MCP in open beta; GA announced for 30 Sep 2026. |
| PandaDoc | Remote https://mcp.pandadoc.com/v1/mcp (EU: mcp.pandadoc.eu) |
Custom / OAuth hosted connector | Any host that can hit a remote MCP URL | Not published as a structural block | Included with an existing PandaDoc account; no separate MCP fee |
| BoldSign | Hosted regional, including AU https://mcp-au.boldsign.com/mcp |
Claude web OAuth; editors via API key | Remote HTTP + X-API-Key if the client allows headers |
Not published as a structural block | API key or OAuth on the regional endpoint you already use |
| SignNow | stdio Python + remote https://mcp-server.signnow.com/mcp |
Custom / local | Remote URL if the client supports it | Not published as a structural block. 18 tools including embedded signing. | MCP on paid airSlate SignNow plans; free trial documented |
| SignWell | stdio npx @signwell/mcp |
Connectors Directory (one-click in Claude Desktop) | No remote URL published | Not published as a structural block | API access requires a paid plan |
| Signvoy | Remote https://api.signvoy.com/mcp |
Custom connector, OAuth 2.1 + DCR | Remote URL | Create and send are separate tools. Prompt says never skip human review. Not a cryptographic block on the key. | Free tier; 13 outcome-shaped tools; embedded signing links |
| Signbee | stdio npx signbee-mcp |
Local Desktop / Cursor | No remote URL published | One send_document tool. Designed for autonomous dispatch. Two-party. |
5 docs/mo free, then $0.50/doc |
| DocuSeal | npm / self-host | Local / self-hosted MCP | Only if you expose the server | You own the model. Self-host means you own deliverability and evidence too. | OSS + sandbox; you run Docker |
| eID Easy | npm package | Local | Not a Grok Bot listing | QES via 80+ European trust providers. Different legal tier, not a convenience MCP. | Trial; QES is the product |
Also-ran rows we are not pretending to have production-tested: SendSign (open-source, Cowork plugin, 17 tools on SumoSign’s own compare page), DottedSign (remote https://mcp.dottedsign.com/dottedsign-api/mcp), DocsAutomator (17 tools), Signaturit, Papersign, Autenti via Zapier. If your counterparty already lives there, use their server. Do not pick them because a roundup needed eight logos.
Can the AI agent complete the signature?
Ask this before you ask how many tools the server exposes. Tool count is a bad proxy. SignNow’s 18 tools and DocsAutomator’s 17 include folder CRUD and merge steps that compete for context. Anthropic’s own MCP server guidance prefers fewer outcome-shaped tools. The failure that matters is an agent that can both send and sign.
SumoSign’s rule is structural. The ss_live_… key authenticates the agent. Scopes cover create, send, download, templates, webhooks, audit. Completing a signature requires the recipient’s one-time token from the emailed link, with consent captured, IP and user agent logged, on the public /v1/sign/{token} routes. The MCP send_envelope tool cannot complete a signature. The audit trail records actor type: user, api_key, recipient, or system.
Signvoy splits create from send and tags MCP actions actorSource: "mcp". That shrinks blast radius to a draft. It is still a policy plus a second tool call, not a second credential. Docusign’s beta docs tell you a human should confirm tool calls and warn that fully automated agents raise prompt-injection risk. They do not publish “this credential is incapable of signing.” Signbee markets a single atomic send_document call for autonomous dispatch. Fine for a two-party NDA you are willing to let the model fire. Not fine for a multi-party MSA.
If a vendor will not state, in text, that the agent credential cannot complete a signature, assume it can.
How do you connect Claude versus Grok Bot?
Claude has two paths. The Connectors Directory is the in-chat catalog. Verified and community connectors show up as Suggested Connectors. Submitting requires a Team or Enterprise organisation and Owner (or delegated Directory) access inside Claude.ai admin settings. Individual Pro/Max plans cannot submit. Docusign and SignWell are in that catalog. SumoSign is not, because we do not have that org yet. Compatible and listed are different sentences.
The path that works without a directory listing is Customize → Connectors → Add custom connector. Paste the remote URL. SumoSign uses OAuth at the MCP origin for Claude. Header-key clients keep using Authorization: Bearer ss_live_….
Grok Bot is a cloud computer with a plugin catalog. Docusign is already in that catalog via its official remote MCP. SumoSign is added as a custom plugin: Settings → Plugins → Add custom → URL https://mcp.sumosign.app/mcp → header Authorization: Bearer ss_live_YOUR_KEY. The same URL works at grok.com → Connectors → New Connector → Custom. Grok Build’s official marketplace is a separate GitHub PR to xai-org/plugin-marketplace. That is not required for a Bot to call the server.
Cursor and Claude Desktop still run the stdio package if you want file-path preview tools on the laptop:
{
"mcpServers": {
"sumosign": {
"command": "npx",
"args": ["-y", "@sumosign/mcp"],
"env": { "SUMOSIGN_API_KEY": "ss_live_YOUR_KEY_HERE" }
}
}
}Remote config for hosts that speak Streamable HTTP:
{
"mcpServers": {
"sumosign": {
"url": "https://mcp.sumosign.app/mcp",
"headers": {
"Authorization": "Bearer ss_live_YOUR_KEY_HERE"
}
}
}
}Docusign’s remote URL is easier to paste than its OAuth. Production is https://mcp.docusign.com/mcp. Demo is https://mcp-d.docusign.com/mcp. You still create an Integration Key, a client secret, and both Claude redirect URIs. Cursor users have reported the demo/prod gateways returning HTTP 403 without WWW-Authenticate, which blocks spec-compliant OAuth starts. Docusign staff have called that a known beta defect. Budget an hour, and a fallback bearer token, if DocuSign is mandatory.
How does SumoSign’s remote MCP work?
The hosted server is stateless Streamable HTTP into the same REST API as the dashboard. Tool names match the stdio package, plus get_billing and create_checkout_link. Remote upload takes { filename, bytesBase64 } or an HTTPS URL (PDF, 25 MB). Preview and download tools return short-lived tokenized HTTPS URLs instead of writing local files, because a cloud bot has no disk you own.
Create and send accept Idempotency-Key. Agents retry. Without that header, a timeout becomes a second envelope to your counterparty. Envelope statuses are draft, sent, viewed, partially_signed, completed, voided, expired. Routing is parallel or sequential. Evidence on completion is the flattened PDF, the Certificate of Completion, and the append-only audit trail, all over the same API.
Pricing is one envelope counter across dashboard, API, and MCP. Starter is $79/month for 100 envelopes. Professional is $249/month for 1,000. Enterprise from $799/month. No per-seat line. Sends pause at the cap after an 80% warning email; they do not silently overage. Trial is 30 days, 25 envelopes, no card. When it ends, the account goes read-only for 12 months. Those are SumoSign’s published numbers as of 6 September 2026.
Honest limits: newer brand, smaller integration marketplace than Docusign, no EU QES, custom signing domains only on Enterprise, Claude directory listing blocked on our Anthropic plan, Grok Bot marketplace catalog not submitted. The remote URL and the two-credential rule are the product; directory badges are a later queue.
Which tool should you pick?
Counterparties contractually require Docusign. Use Docusign MCP. You are buying the ecosystem and the directory listing. You are also buying beta behaviour until 30 September 2026, Integration Key ceremony, and per-seat plus API plan gates. Do not migrate a live DocuSign estate to look modern.
You need Qualified Electronic Signatures under eIDAS. eID Easy. Nobody else in this table is in that tier. SES-style click-to-sign MCP servers will not satisfy a QTSP requirement.
Data has to stay on your metal. DocuSeal. You own Docker, SMTP, backups, and the evidence burden.
A two-party NDA from Markdown in one tool call. Signbee. Local stdio, 5 free docs/month, then $0.50 each. No multi-party routing worth using for an MSA.
Embedded signing inside your own product, fast OAuth. Signvoy (DCR, one Allow click) or SignNow (embedded tools, Python or hosted URL). Docusign, PandaDoc, BoldSign, and SignWell do not expose embedded signing through MCP on Signvoy’s July check.
Already living in PandaDoc proposals. PandaDoc’s hosted MCP. Keep the API key out of git if you are still on the static-header path.
Australian BoldSign account. Use https://mcp-au.boldsign.com/mcp, not the US host. Residency follows the account region.
Agent prepares, routes, and tracks multi-party envelopes; humans sign; Claude custom connector and Grok Bot custom plugin; flat envelope price with API included. SumoSign. That is the job we built it for. If you need the Claude directory icon before you will try a custom connector, wait, or stay on Docusign.
What should you verify before you wire production?
- Remote URL answers over HTTPS from the agent host, not only from your laptop.
- The agent credential cannot hit the complete-signature route. Test it. Do not take the README’s word if the vendor is vague.
- Create and send are idempotent, or you will double-send on retries.
- Audit events name the actor type. “API” as a single blob fails an incident review.
- Completed PDF, certificate, and audit trail are retrievable through the same credential the agent already holds.
- Envelope economics at agent volume. Per-seat products were priced for humans clicking. Agents send more envelopes and do not sit in a named seat.
We run that checklist against SumoSign because we operate it. We have not sat inside Docusign IAM, PandaDoc, or SignNow’s MCP in production this month. Their rows are documentation-based, dated 6 September 2026.
FAQ
Is SumoSign Claude compatible? Yes, as a custom connector. Paste https://mcp.sumosign.app/mcp and complete OAuth. It is not in the Connectors Directory. Directory submission needs a Claude Team or Enterprise org, which we do not have yet. Claude Desktop can also run npx -y @sumosign/mcp.
Is SumoSign Grok Bot compatible? Yes. Settings → Plugins → Add custom, same URL, bearer API key. It is not in Grok Bot’s marketplace catalog. Docusign is. Custom plugins do not wait on a catalog review.
Can an AI agent legally sign a contract? ESIGN and UETA can attribute an electronic agent’s act to the deployer. Most platforms, SumoSign included, still keep the affirmative signing act with a human so intent and consent stay attached to a person. If you need the agent to be the signer, that is a different legal product than any row in this table.
Do I need MCP if I already have a REST API? No, for a deterministic backend job. Yes, if Claude, Grok Bot, or Cursor is the operator and you do not want to maintain a private client. SumoSign’s MCP is a thin layer over the same REST resources, so they do not drift.
Why is Docusign in every catalog and SumoSign is not? Distribution. Docusign partnered with Anthropic on 24 February 2026 and sits in Claude’s directory and Grok Bot’s plugin list. We shipped the remote URL. Listing is a separate queue: Claude Team/Enterprise for the directory, a marketplace PR for Grok Build, and an in-app catalog for Grok Bot. The protocol already works.
Which platforms have MCP in 2026? Official remote or stdio servers we can name from vendor docs: Docusign, PandaDoc, BoldSign, SignNow, SignWell, Signvoy, Signbee, DocuSeal, eID Easy, DottedSign, SendSign, DocsAutomator, and SumoSign. Autenti is middleware. Adobe Acrobat Sign and Dropbox Sign still look like REST-plus-wrapper.
Who should wire this into a production agent? If you only need envelopes, start the SumoSign trial and paste the MCP URL. If you need the agent platform around it (identity, evals, connectors, audit beyond signing), Cipher Projects is the studio that built SumoSign and ships production agents for Australian and Singapore teams. We will tell you when DocuSign is the correct answer.
Related: How solo founders build production AI agents · n8n vs Zapier pricing 2026 · MCP vs A2A vs ACP vs AP2 · DocuSign MCP on SumoSign · Applied AI Engineering
Paste https://mcp.sumosign.app/mcp into Claude or Grok Bot and send one envelope. The key will not sign it for you.