Dropbox Sign MCP Server

Dropbox Sign

Dropbox Sign (formerly HelloSign) is an electronic signature platform for sending, signing, and managing legally binding documents. It replaces paper-based signing workflows with tracked digital signature requests.

Core Concepts

• Signature requests are the primary unit of work. A request packages one or more documents, assigns signers (by email or template role), and tracks each signer through awaiting_signature → signed or declined states. Each request has a unique signature_request_id.
• Templates are reusable document blueprints with predefined signer roles, field placements, and merge fields. Create a signature request from a template to avoid re-uploading and re-configuring documents every time.
• Account represents your Dropbox Sign user — includes email, quota usage (API requests remaining, documents remaining, templates remaining), callback URL, and plan status.

Workflows

• Review pending signatures: Enumerate signature requests and filter by status to find documents awaiting action.
• Track one request: Open a signature request by id for signer status, response data, custom fields, and timestamps.
• Manage templates: Enumerate templates for reusable layouts, or open one template to inspect signer roles and merge fields before creating a request.
• Monitor usage: Retrieve account details to see remaining API quotas and plan information.

Pagination

Long lists of signature requests and templates return page metadata (current page, total pages, counts, page size) so you can walk the full set without assuming everything fits one response. Page size caps at 100.

Search / Filtering

Optional filters narrow lists using field-style terms (e.g. status, sender, recipient, title). Multiple terms combine with AND logic.

Gotchas

• Sandbox or empty accounts can return empty lists until real signature requests and templates exist.
• Signer ordering: Templates can enforce signer order (first signer must complete before second receives the request).
• Custom fields / merge fields: When creating a request from a template, pass custom_fields to pre-fill merge fields defined in the template.
• Rate limits: Per-minute ceilings apply—slow down when responses signal throttling.