@bossforce.ai/mcp-dropbox-sign

MCP server for the Dropbox Sign (formerly HelloSign) eSignature REST API, using API key authentication. A good fit for sending documents and templates out for electronic signature and tracking signature requests from an agent.

Credentials

| Env | Secret | How to obtain | | ---------------------- | ------ | ----------------------------------------------------------------------------------------------------------- | | DROPBOX_SIGN_API_KEY | yes | In Dropbox Sign, open Settings > API and create an API key. |

Credentials are read lazily, so the server boots and answers tools/list without them; calls fail with an auth error until the key is set.

Authentication uses HTTP Basic auth, encoding {api_key}: (the API key as the username with an empty password). The API base URL is https://api.hellosign.com/v3. Sending binding requests requires a paid API plan; use test_mode for non-binding requests while developing.

Tools

| Tool | Arguments | Returns | | ------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------- | | send_signature_request | signers, file_urls, title?, subject?, message?, cc_email_addresses?, test_mode? | { signature_request } | | send_with_template | template_ids, signers, subject?, message?, test_mode? | { signature_request } | | get_signature_request | signature_request_id | { signature_request } | | list_signature_requests | account_id?, page?, page_size?, query? | { signature_requests, list_info } |

Responses are Dropbox Sign's native JSON payloads, returned as structuredContent.

Sending for signature

send_signature_request takes the signers and the documents as file_urls (publicly accessible URLs — file uploads are not supported by this server). send_with_template takes template_ids and assigns signers to the template roles by role name.

Tracking

get_signature_request returns a single request by id, including each signer and whether it is complete. list_signature_requests is paginated (page, page_size) and accepts a Dropbox Sign search query, e.g. complete:true or to:[email protected].

Develop

pnpm --filter @bossforce.ai/mcp-dropbox-sign build
pnpm --filter @bossforce.ai/mcp-dropbox-sign test

Regenerate the tools/list snapshot after an intentional signature change:

UPDATE_SNAPSHOTS=1 pnpm --filter @bossforce.ai/mcp-dropbox-sign test