How to Connect Dropbox Sign to Claude (and What It Can't Do)
Start with the naming trap, because it catches almost everyone: the Dropbox connector in Claude’s directory has nothing to do with Dropbox Sign. That first-party connector covers Dropbox file storage — searching folders, reading and organizing files. Dropbox Sign (the e-signature product, formerly HelloSign) runs on a separate API with separate credentials, and as of mid-2026 it has no listing in Anthropic’s connector directory and no official MCP server from Dropbox itself.
What does exist: community MCP servers that wrap the Dropbox Sign API — Smithery hosts one — which you add to Claude as a custom connector. Custom connectors require a paid Claude plan, and like every Claude connector, they respond only inside a conversation you open. Nothing watches your signature requests between chats.
What a community server wraps
The Dropbox Sign API is built around signature requests. You send one (from an uploaded file or a reusable template), list the requests in flight, remind a signer, cancel a request, and download the completed PDF along with its audit trail — the timestamped record of who signed what, when, and from where. A community MCP server maps those endpoints to tools Claude can call, authenticated with an API key you generate in your Dropbox Sign account settings.
Two Dropbox Sign specifics worth knowing before you wire anything up:
- Legally binding sends require a paid Dropbox Sign API plan. Free accounts can exercise nearly every endpoint with
test_modeenabled, but test-mode requests carry no legal weight. If Claude “sends an NDA” through a free-tier key, nothing has actually been executed — a distinction that matters a great deal in this product category. - You’re trusting community code with signing authority. An API key that can send signature requests can bind your company to contracts. Read the server’s source (or self-host your own) before handing it that key.
Setup itself is short: generate the API key, run or point at the MCP server, then add it in Claude under Settings → Connectors as a custom connector and approve the tool permissions.
Prompts that make sense once it’s connected
- “Which signature requests are still out, and which signer is each one waiting on?”
- “Send our standard NDA template to the subcontractor I onboarded this morning — test mode first so I can check the field placement.”
- “Pull the completed office lease from last week and summarize the audit trail: who signed, in what order, from which email addresses.”
That last one is where a chat interface genuinely shines. Audit trails are dense, and having Claude read one back in plain language beats scanning the PDF appendix.
The gap between asking and happening
Every one of those prompts shares a hidden requirement: you, in the chat, typing. The moments that actually decide whether contracts close tend to arrive when you’re not there.
The consulting agreement you sent Monday is still unsigned Thursday — nobody nudges the signer unless you open Claude and think to ask. A client countersigns at 9 p.m. — the completed PDF and its audit trail don’t file themselves to the deal folder, and the kickoff email doesn’t go out. A new client says yes on a call — the signature request that should go out within the hour waits for you to get back to a keyboard. Claude’s connectors have no listener for signed-request events, no scheduler, no way to run while the chat window is closed.
Handing the follow-through to Carly
Carly is an AI executive assistant designed around exactly those unattended moments. It runs in the cloud and fires on events: when a client agrees, Carly sends the signature request from your template; when a request stalls, it drafts and sends the reminder; when the document completes, it files the signed copy, updates your CRM, and notifies the team — with your email, calendar, and task tools in the same workflow.
You don’t configure any of this with API calls. Describe the outcome (“send our NDA whenever a new client is added to the pipeline, and chase it after three days”), and Carly interviews you about the details, then builds the workflow with you. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See the Dropbox Sign integration page and the full integrations list.
Claude with a Dropbox Sign server vs Carly
| Claude (community MCP) | Carly | |
|---|---|---|
| Check in-flight signature requests | Yes, when you ask | Yes, continuously |
| Send from a Dropbox Sign template | Yes (in chat) | Yes (on a trigger) |
| Nudge a signer stalled for three days | Only if you remember to ask | Automatic |
| File the signed PDF + audit trail on completion | No | Yes |
| Official, maintained integration | No (community server) | Yes |
| Runs while the chat is closed | No | Yes (cloud) |
| Pricing | Paid Claude plan (+ paid Sign API plan for binding sends) | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with Dropbox Sign?
Not officially. As of mid-2026 there’s no Dropbox Sign entry in Claude’s connector directory and no vendor-built MCP server. You connect through a community MCP server that wraps the Dropbox Sign API, added as a custom connector — which needs a paid Claude plan — and it works only inside chats you start.
Isn’t Dropbox already in Claude’s connector directory?
Yes, but that connector is for Dropbox file storage — it can search and read your files. It cannot see or send Dropbox Sign signature requests, which live behind a different API.
Can Claude send a legally binding signature request?
Only if the connected API key belongs to a paid Dropbox Sign API plan; free keys are limited to test mode, which isn’t legally binding. And even then, Claude sends only when you ask it to mid-conversation and approve the tool call.
Why won’t Claude remind my signer after a few days?
Because connectors have no triggers or schedules — they execute during a live chat and stop when it ends. Time-based follow-up needs an agent that runs on its own, like Carly.
What can Carly do with Dropbox Sign that Claude can’t?
React to events: send a request the moment a client commits, chase stalled signers on a cadence, and file completed agreements automatically, 24/7 in the cloud. AI agents start at $35/month, and non-AI steps in a workflow run free and unlimited.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Best AI tools for solopreneurs · Claude + PandaDoc · Claude + BoldSign · Claude + DocuSeal
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."
