Connect Dropbox Sign to Claude Code

Let Claude build and send signature requests in Dropbox Sign. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Dropbox Sign to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Dropbox Sign, you add a Dropbox Sign MCP server: a small hosted service that exposes Dropbox Sign's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Dropbox Sign account. No API keys pasted into config files.

claude mcp add --transport http dropbox-sign https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Dropbox Sign once connected?

Full read-write Dropbox Sign access lets Claude build a signature request from a template, add signers and a signing order, place signature and date fields, and send it for signature once you approve. The document prep that used to mean clicking through the Dropbox Sign dashboard happens where the request already started.

Create a signature request from a template and populate its fields
Add signers and set a signing order on a request
Place signature, initial, and date fields for each signer
Send a prepared signature request after you approve it
Send a reminder to a signer who has not yet signed
Cancel a signature request that was sent in error, with your confirmation

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Dropbox Sign access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Dropbox Sign API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Dropbox Sign changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Dropbox Sign connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Dropbox Sign connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Dropbox Sign account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Dropbox Sign's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Dropbox Sign?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Dropbox Sign account it signs in with. Revoking access is one click in Dropbox Sign.

More on the Dropbox Sign connector

Dropbox Sign connector for claude.ai DocuSign + Claude Code PandaDoc + Claude Code Adobe Acrobat Sign + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us