How to Connect DocuSeal to Claude (and What It Can't Do)
Of all the e-signature tools in this series, DocuSeal — the open-source one — took the most direct approach to MCP: it built the server into the product. There’s no wrapper to vet and no npm package to babysit. Cloud users will find DocuSeal listed in Claude’s connector directory as of mid-2026; self-hosters get something rarer — their own instance serves MCP directly at https://yourdomain.com/mcp, authenticated with a token generated under Settings → MCP Server, per DocuSeal’s MCP guide.
One routing note for self-hosters. Claude’s web app expects OAuth on remote connectors, and OAuth support on the self-hosted endpoint is still an open request on DocuSeal’s tracker (issue #630) — so a token-authenticated instance connects most smoothly from Claude Desktop or Claude Code. And whichever route you take, the standard Claude connector rules hold: custom connectors need a paid Claude plan, and the connection does nothing outside a chat you’ve opened.
Five tools, including two writes
DocuSeal keeps the surface small and legible:
search_templates— find templates by name.load_template— pull a template’s fields and signer roles.search_documents— find submissions, signed or still pending.create_template— build a new fillable template from a PDF or DOCX.send_documents— send for signature, with fields prefilled.
The sleeper here is create_template. Hand Claude a contractor agreement PDF in a chat and it can produce a DocuSeal template with signature, date, and text fields assigned to the right roles — the tedious part of adopting any e-signature tool. Combined with send_documents and prefill, a surprising amount of real signing work fits in one conversation:
- “Turn this consulting agreement PDF into a DocuSeal template with signature and date fields for two roles: client and contractor.”
- “Search this month’s submissions for the vendor W-9 template — who hasn’t finished theirs?”
- “Send the onboarding packet template to the three hires starting Monday and prefill their names and start dates.”
Self-hosting the stack doesn’t make Claude watch it
Here’s the irony DocuSeal self-hosters run into. You control the entire signing pipeline — the server, the data, the webhooks it fires when a submission completes or a submitter opens a document. But Claude has nowhere to receive any of that. A connector participates in conversations; it cannot subscribe to your instance’s events or check anything on a schedule.
So the workflows people actually want stay out of reach: archiving the signed PDF to Drive and pinging the team channel when a submission completes, chasing a submitter who’s been sitting on an onboarding packet since Tuesday, or emailing you a completion report when the last person in a compliance batch signs. Each of those starts with a DocuSeal event, and events are precisely what a chat can’t hear.
Pointing the events at Carly instead
That’s the half Carly covers. Carly is an AI executive assistant that runs in the cloud and is built around triggers — a submission completing, a document stalling, a schedule elapsing — and it acts across your other tools in the same workflow: it sends email (Gmail and Outlook, with attachments), files documents, posts to Slack, updates tasks and your CRM.
Building the workflow is conversational: say “when everyone in an onboarding batch has signed in DocuSeal, email me the packet and post a summary to #people-ops,” and Carly asks the clarifying questions, then assembles and runs it 24/7 — no MCP endpoint for you to maintain on that side. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. There’s a dedicated DocuSeal integration page, and 200+ other tools under integrations.
What lands where: Claude’s DocuSeal tools vs Carly
| Claude (DocuSeal MCP) | Carly | |
|---|---|---|
| Create templates from PDF/DOCX | Yes, in chat | No — that’s a chat job, and Claude does it well |
| Search templates and submissions | Yes, when you ask | Yes, continuously |
| Send documents with prefilled fields | Yes (you approve) | Yes (on a trigger) |
| React when a submission completes | No | Yes |
| Chase a submitter stalled since Tuesday | Only if you think to ask | Automatic |
| Runs unattended, laptop closed | No | Yes (cloud) |
| Pricing | Paid Claude plan | AI agents from $35/mo |
The honest split: Claude plus DocuSeal’s MCP server is genuinely good at the interactive work — template creation especially. Carly exists for everything that should happen when nobody’s in a chat.
Frequently Asked Questions
Does Claude integrate with DocuSeal?
Yes. DocuSeal ships first-party MCP support: cloud accounts appear in Claude’s connector directory as of mid-2026, and self-hosted instances expose their own /mcp endpoint with a token from Settings → MCP Server. Custom connectors require a paid Claude plan, and the integration operates only inside chats you start.
Can I connect a self-hosted DocuSeal instance to Claude?
Yes — point Claude Desktop or Claude Code at https://yourdomain.com/mcp with your MCP token as a bearer header. The claude.ai web app is trickier because its custom connectors expect OAuth, which self-hosted DocuSeal doesn’t yet offer.
Can Claude create DocuSeal templates?
Yes, and it’s the standout feature: the create_template tool turns a PDF or DOCX into a fillable template with fields and signer roles, all from a chat.
Can Claude do something when a submission completes?
No. DocuSeal fires webhooks on completion, but Claude has no way to receive them — connectors can’t listen for events. Completion-driven filing, notifications, and follow-ups are what Carly handles.
Does Carly replace the DocuSeal MCP server?
They cover different halves. Keep Claude’s connector for interactive work like building templates; use Carly for the trigger-driven workflows — chasing signers, filing signed documents, completion alerts. AI agents start at $35/month, with non-AI steps free and unlimited.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Claude contract review · Claude + Tally · Claude + Dropbox Sign · Claude + PandaDoc
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
