DocuSeal
by DocuSeal
Create signing templates and send documents for electronic signature from your AI assistant. One tool emails a legally-binding signature request to a third party with no confirmation step, and its own source code annotates it destructive.
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.
Connect DocuSeal via MCP
https://docuseal.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
DocuSeal Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
send_documentsemails third parties on the call, with no confirmation gate. DocuSeal documents that submitters receive an email; the source sets the send flag unconditionally. Your MCP client's approval prompt is the only gate.- No undo. The five tools include no cancel, void, or delete operation. A mistaken send cannot be fixed by another tool call.
- Prefilled fields are locked to the signer. The source marks caller-supplied values read-only, so a recipient cannot correct a wrong value the agent entered.
- No named OAuth scopes.
scopes_supportedis absent from both the resource descriptor and the authorization-server metadata, so access cannot be narrowed to reads. - No dynamic client registration advertised. The RFC 8414 metadata names no registration endpoint.
- The vendor's MCP documentation is for self-hosted only. Its banner says so, yet it is the documentation URL published for the hosted connector.
- Anthropic's snapshot lists four of five tools.
load_templateis absent from the directory record but documented and implemented. - The MCP surface is a fraction of the REST API. Roughly twenty-two documented REST operations versus five tools — no submitter updates, no archiving, no webhook management from an agent.
- A template must have fields before it can be sent. DocuSeal's error table names this explicitly; a freshly created empty template will fail a send.
- Free-plan email sending is capped at 10 per month. DocuSeal documents 10 signature-request emails per month on Basic, unlimited on Pro at $20 per user per month, and notes the cap does not apply to the on-premises version.
- SMS costs extra. DocuSeal lists a $0.20 fee per SMS on the Pro plan.
- Advanced and Qualified eIDAS signatures cost extra per signature. DocuSeal states these are available through partnered qualified trust service providers at additional cost.
- No prompts and no resources. Anthropic's snapshot lists no prompts, and DocuSeal's server declares only a
toolscapability in its source — soprompts/listandresources/listare not offered surfaces. - We did not read the live schemas. The hosted endpoint returned 401 to an anonymous handshake. Tool names, schemas and annotations here come from DocuSeal's documentation and its open-source implementation, not from a wire response.
Frequently asked questions
Does the DocuSeal MCP server actually email signature requests?
Yes. DocuSeal documents that each submitter receives an email containing a link to sign the document, and the open-source implementation of the tool sets the send-email flag to true unconditionally before dispatching signature requests. There is no draft mode and no parameter that stages a submission without sending it. One tool call puts mail in a third party's inbox.
Is there a confirmation step before a document goes out?
No confirmation gate exists inside the connector. DocuSeal's guide documents no preview, no dry-run parameter and no approval step, and the source code dispatches immediately after creating the submission. The only protection is your MCP client's own tool-approval prompt, so leave that enabled. The tool is annotated destructive, which well-behaved clients surface as a warning.
Can you un-send a DocuSeal signature request?
Not in the sense of recalling the email. None of the five MCP tools offers a cancel, void or delete operation at all, so an agent that sends cannot undo it. DocuSeal's REST API can archive a submission and permanently delete one with an explicit query parameter, but the notification already delivered stays delivered and any completed signature stays completed.
Are documents signed through DocuSeal legally binding?
DocuSeal states its platform aligns with UETA, the ESIGN Act and eIDAS, and that signed documents are enforceable in court. It documents email or SMS signer authentication, an automatically generated Certificate of Signature recording timestamps and IP addresses, and support for all three eIDAS signature levels. Treat that as the vendor's stated position and consult a lawyer about your own use.
Is creating a DocuSeal template through MCP a safe operation?
Largely, yes. The create-template tool is annotated as not destructive in DocuSeal's source, and it produces a document shell rather than contacting anyone. Two side effects are worth knowing: it fires a template-created webhook to any configured endpoint, and supplying a URL makes DocuSeal's servers fetch that file. Nothing is emailed to a signer.
Does the hosted DocuSeal MCP server work the same way as self-hosted?
No, and the difference starts at authentication. DocuSeal's MCP guide carries a banner saying it covers the self-hosted version only, and describes a bearer token minted in settings. The hosted endpoint at docuseal.com answered our anonymous probe with an OAuth challenge instead. Self-hosters also get their own domain and an account-level enable switch.
How many tools does the DocuSeal MCP server expose?
Five, not the four in Anthropic's directory snapshot. DocuSeal's guide and its open-source controller registry both list a template-loading tool that the snapshot omits. Five is a deliberately narrow surface over a much wider REST API of roughly twenty-two documented operations, so most DocuSeal functionality is unreachable from an agent.
Sources
- DocuSeal MCP guide — https://www.docuseal.com/guides/integrate-with-ai-agents-using-mcp (fetched 2026-08-19; this is the
documentationURL in Anthropic's directory, and it carries a banner stating it covers the self-hosted version only). Appending.mdreturnstext/markdownbut a 500 error page, so the HTML was used · retrieved 2026-08-19 - DocuSeal Security & Compliance — https://www.docuseal.com/compliance (fetched 2026-08-19) · retrieved 2026-08-19
- DocuSeal on UETA and the ESIGN Act — https://www.docuseal.com/blog/how-docuseal-ensures-compliance-with-ueta-and-the-esign-act (published 25 November 2024, fetched 2026-08-19) · retrieved 2026-08-19
- Certificate of Signature (Audit Log) — https://www.docuseal.com/faq/what-is-the-certificate-of-signature-audit-log (fetched 2026-08-19) · retrieved 2026-08-19
- Can I revoke a signature in a PDF? — https://www.docuseal.com/faq/can-i-revoke-a-signature-in-a-pdf (fetched 2026-08-19) · retrieved 2026-08-19
- How to permanently delete a submission via the API — https://www.docuseal.com/faq/how-to-permanently-delete-a-submission-via-the-api (fetched 2026-08-19) · retrieved 2026-08-19
- Can I send an unlimited number of documents for signing? — https://www.docuseal.com/faq/can-i-send-an-unlimited-number-of-documents-for-signing (fetched 2026-08-19; 10 emails per month on Free, no cap on Pro or on-premises) · retrieved 2026-08-19
- DocuSeal pricing — https://www.docuseal.com/pricing (fetched 2026-08-19; Pro $20 per user per month, SMS $0.20 each) · retrieved 2026-08-19
- DocuSeal REST API Reference — https://www.docuseal.com/docs/api (fetched 2026-08-19; roughly 22 documented operations across submissions, submitters, templates and webhooks) · retrieved 2026-08-19
- DocuSeal source, MCP tool registry — https://github.com/docusealco/docuseal/blob/master/app/controllers/mcp_controller.rb (fetched 2026-08-19; five tool names mapped to five controllers; server declares only a
toolscapability) · retrieved 2026-08-19 - DocuSeal source,
send_documentshandler — https://github.com/docusealco/docuseal/blob/master/app/controllers/mcp/send_documents_controller.rb (fetched 2026-08-19;'send_email' => truehard-coded,destructiveHint: true) · retrieved 2026-08-19 - DocuSeal source,
create_templatehandler — https://github.com/docusealco/docuseal/blob/master/app/controllers/mcp/create_template_controller.rb (fetched 2026-08-19;destructiveHint: false, enqueues a template-created webhook) · retrieved 2026-08-19 - DocuSeal source, MCP base controller — https://github.com/docusealco/docuseal/blob/master/app/controllers/mcp/mcp_base_controller.rb (fetched 2026-08-19; account-level MCP check skipped in multitenant mode; self-hosted auth by SHA-256 bearer token) · retrieved 2026-08-19
- DocuSeal repository metadata — https://api.github.com/repos/docusealco/docuseal (fetched 2026-08-19; licence AGPL-3.0) · retrieved 2026-08-19
www.docuseal.com/robots.txtanddocuseal.com/robots.txtare bothAllow: /with noContent-Signalheader on either (fetched 2026-08-19).www.docuseal.com/llms.txtreturns 404; the page inventory came from the sitemap named inrobots.txt· retrieved 2026-08-19- Live RFC 9728 protected-resource descriptor — https://docuseal.com/.well-known/oauth-protected-resource/mcp (fetched 2026-08-19; the root form returns a 1-byte whitespace 200, the path-insert form returns 404). No
scopes_supportedkey · retrieved 2026-08-19 - Live RFC 8414 authorization-server metadata — https://docuseal.com/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer
https://docuseal.com/, noscopes_supported, no registration endpoint) · retrieved 2026-08-19 - Live anonymous probe — 2026-08-19: an anonymous POST to
https://docuseal.com/mcpreturns HTTP 401 withwww-authenticate: Bearer resource_metadata="https://docuseal.com/.well-known/oauth-protected-resource/mcp". No tool was ever called · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/62270356-d0aa-46fc-a0bf-e57af079104d (snapshot 2026-08-16; permissions "Read and write", 4 tool names, no prompts) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- DocuSeal
- Tools
- 5
- Domain
- docuseal.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.