Dropbox Sign MCP server
Dropbox Sign in any MCP client, through Memtro: Dropbox Sign does not publish this server. Memtro's Dropbox Sign connector reads Dropbox Sign through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Dropbox Sign (HelloSign): signature requests with title, status (awaiting signature, complete, declined, expired), who has signed and when, searchable by title, signer, sender and creation date, and templates with their signer roles; and, when granted, send a request from a template or from document URLs, remind a signer, correct a signer's name or address, cancel an incomplete request, or remove this account's access to a completed one.
Reads
dropboxsign_list_signature_requestsSignature requests the account sent or received, with title, status, created and expiry dates, and each signer's name, company domain…dropboxsign_get_signature_requestOne signature request in detail: title, subject, message, status, dates, the templates it used, and every signer's name, company domain, role, order…dropboxsign_list_templatesTemplates the account can use: title, message, when last updated, and whether this account created it or can edit it.dropboxsign_get_templateOne template: title, default message, its signer roles (with signing order) and CC roles that a send must fill…
Acts, when you ask
These change something in Dropbox Sign. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
dropboxsign_send_with_templateSend a signature request built from one or more saved templates.dropboxsign_send_signature_requestSend documents for signature.dropboxsign_send_reminderEmail one signer a reminder to sign an open request.dropboxsign_update_signerCorrect a signer on an open request: a new email address (which emails the new address the request and gives the signer a new signature id)…dropboxsign_cancel_signature_requestCancel an incomplete signature request (partly signed is allowed).dropboxsign_remove_signature_request_accessRemove this account's own access to a fully executed (signed or declined) signature request.
Connect it
First connect Dropbox Sign on Dashboard → Connections, then add Memtro to your client once. The Dropbox Sign tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Dropbox Sign connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Has Northwind signed the MSA yet?
- › What is still awaiting signature across the team?
- › Why did BigCo decline the order form?
- › Remind the second signer on the Northwind renewal to sign
- › Send the standard NDA template to Laura Bennett at Globex for signature
Questions
- Is this an official Dropbox Sign MCP server?
- No. It is Memtro's MCP server with Memtro's Dropbox Sign connector behind it: the connector reads Dropbox Sign through its API with the credentials you connect on Dashboard → Connections, and Dropbox Sign publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Dropbox Sign?
- Only when you ask, and only what it has been granted: send a signature request from a template to named signers (emails them a signing link); send a signature request for documents at URLs to named signers (emails them a signing link); remind a signer by email to sign an open request; change a signer's name or email address, or a request's expiry; cancel an incomplete signature request (permanent); remove this account's access to a completed signature request (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.