6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Create signing templates and send documents for e-signature.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The DocuSeal MCP server lets Claude, ChatGPT or any MCP-compatible agent search signing templates, build new ones from a PDF, and send documents out for electronic signature. Five tools cover the whole surface. One of them emails a legally-binding signature request to a real person, immediately, with no confirmation step in the connector.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
send_documents emails 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.scopes_supported is absent from both the resource descriptor and the authorization-server metadata, so access cannot be narrowed to reads.load_template is absent from the directory record but documented and implemented.tools capability in its source — so prompts/list and resources/list are not offered surfaces.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.
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.
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.
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.
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.
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.
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.
documentation URL in Anthropic's directory, and it carries a banner stating it covers the self-hosted version only). Appending .md returns text/markdown but a 500 error page, so the HTML was used · retrieved 2026-08-19tools capability) · retrieved 2026-08-19send_documents handler — https://github.com/docusealco/docuseal/blob/master/app/controllers/mcp/send_documents_controller.rb (fetched 2026-08-19; 'send_email' => true hard-coded, destructiveHint: true) · retrieved 2026-08-19create_template handler — 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-19www.docuseal.com/robots.txt and docuseal.com/robots.txt are both Allow: / with no Content-Signal header on either (fetched 2026-08-19). www.docuseal.com/llms.txt returns 404; the page inventory came from the sitemap named in robots.txt · retrieved 2026-08-19scopes_supported key · retrieved 2026-08-19https://docuseal.com/, no scopes_supported, no registration endpoint) · retrieved 2026-08-19https://docuseal.com/mcp returns HTTP 401 with www-authenticate: Bearer resource_metadata="https://docuseal.com/.well-known/oauth-protected-resource/mcp". No tool was ever called · retrieved 2026-08-19Connect DocuSeal once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.