# Dropbox Sign (HelloSign) MCP connector

The Dropbox Sign (HelloSign) connector brings teams, members, bulk send jobs, signing links and fax lines into Elaichi, so Claude, ChatGPT, Cursor and Microsoft Copilot can work with them as the signed-in person, with every call logged.

Source: https://elaichi.ai/connectors/hellosign/

## Facts

| | |
| --- | --- |
| Application | Dropbox Sign (HelloSign) |
| Category | E-Signature |
| AI tools | 72 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Dropbox Sign (HelloSign) is connected

- Which bulk send jobs are still in progress this week?
- List the members on the Sales team in Dropbox Sign
- Get me a signing link for the Acme renewal

## Connect Dropbox Sign (HelloSign) in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Dropbox Sign (HelloSign).
2. Optionally set Share with, then press Connect.
3. Paste a Dropbox Sign (HelloSign) API key. One person generates a token in Dropbox Sign (HelloSign) and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Dropbox Sign (HelloSign) tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Dropbox Sign (HelloSign) MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Dropbox Sign (HelloSign) MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Dropbox Sign (HelloSign) MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Dropbox Sign (HelloSign) MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Dropbox Sign (HelloSign) MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Dropbox Sign (HelloSign) to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Dropbox Sign (HelloSign) tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Dropbox Sign (HelloSign) through Elaichi

### Hand a customer a signing link

Sales. Ask for the signing link on a contract that is waiting and send it on, without opening Dropbox Sign to dig it out.

### Check on a bulk send before the deadline

Operations. Ask which bulk send jobs are still running and pull up the details of one by its ID when a manager asks where things stand.

### Put new hires on the right team

HR. List the teams and members in Dropbox Sign, then move a batch of new starters onto the right team in one go.

### Find where the signature fields belong

Legal. Run field detection on a document to see where the signature and date fields land before it goes out.

### Keep accounts and API apps tidy

IT. List every account and API app, update the ones that changed hands, and delete the ones nobody uses anymore.

### Set up fax lines by area code

Office management. Check which area codes are available, create a fax line for the new office, and add the people who need it.

## Elaichi vs Zapier MCP vs Composio for Dropbox Sign (HelloSign)

All three can connect Dropbox Sign (HelloSign) to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Dropbox Sign (HelloSign) tools | Allow or restrict single Dropbox Sign (HelloSign) tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Dropbox Sign (HelloSign) call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Dropbox Sign (HelloSign) to Claude?

Two steps. In Elaichi, connect Dropbox Sign (HelloSign) by pasting in your Dropbox Sign API key from the HelloSign account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp.

### Does Dropbox Sign (HelloSign) work with ChatGPT and Cursor as well as Claude?

Yes. Once Dropbox Sign (HelloSign) is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect HelloSign once and every client sees it.

### What can an AI agent actually do with my Dropbox Sign (HelloSign) data?

With Dropbox Sign (HelloSign) connected, an agent can list your teams and members, look up a bulk send job and see how it is going, fetch a signing link for a document, detect the fields in a file, manage accounts and API apps, and set up fax lines. Short, concrete asks such as "show bulk send jobs from this week" work better than long sentences.

### Does connecting Dropbox Sign (HelloSign) give the AI access to every team and account?

No. Access to Dropbox Sign (HelloSign) follows the person who signed in to Elaichi, so an agent sees the teams, members and bulk send jobs that person could already see in HelloSign. Elaichi can narrow that access with roles and restrictions, and it never widens it.

### Can my team share one Dropbox Sign (HelloSign) connection?

Yes. One person connects Dropbox Sign (HelloSign) in Elaichi and shares it with a team, and nobody else ever handles the HelloSign API key. Each person still signs in to Elaichi as themselves, so the audit log names who ran each call.

### Can I stop an agent from deleting teams or API apps in Dropbox Sign (HelloSign)?

Yes. In Elaichi, restrictions on Dropbox Sign (HelloSign) are set per action, on a role or on one person, so you can restrict deleting a team or an API app while leaving lookups open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it in HelloSign, whatever the prompt says.

### What happens to a Dropbox Sign (HelloSign) connection when someone leaves?

Offboarding a person in Elaichi ends their access to Dropbox Sign (HelloSign) at once, across every client. A shared HelloSign connection keeps working for everyone else on the team. If you disconnect Dropbox Sign (HelloSign) in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the Dropbox Sign (HelloSign) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Dropbox Sign (HelloSign) is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Dropbox Sign (HelloSign)?

Yes. Both let Claude, ChatGPT or Cursor use Dropbox Sign (HelloSign). Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Dropbox Sign (HelloSign) call.

### How is Elaichi different from Composio for Dropbox Sign (HelloSign)?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Dropbox Sign (HelloSign): one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 72 Dropbox Sign (HelloSign) tools

Every tool below is callable through https://api.elaichi.ai/mcp once Dropbox Sign (HelloSign) is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Dropbox Sign (HelloSign) teams** (List). Get your HelloSign team, including a list of its members. Returns: team_id, team_parent, name, num_members, num_sub_teams. Fails with a 404 error if you do not belong to a team.
- **Get single Dropbox Sign (HelloSign) team by ID** (Get). Get detailed info about a HelloSign team by team id (sent as team_id). Returns: team_id, team_parent, name, num_members, num_sub_teams.
- **Delete a Dropbox Sign (HelloSign) team by ID** (Delete). Remove a user from a HelloSign team, identified by account_id or email_address. Returns the updated team including its name, accounts, invited_accounts, and invited_emails.
- **Dropbox Sign (HelloSign) teams bulk update** (Update). Update the HelloSign team, such as renaming it. Returns the updated team object including its name, accounts, invited_accounts, and invited_emails.
- **List all Dropbox Sign (HelloSign) members** (List). List the members of a Dropbox Sign team and their roles. Returns each member's id and attributes holding the upstream member fields. Required: team_id. Max 100 members per page.
- **List all Dropbox Sign (HelloSign) account** (List). Get the Dropbox Sign account associated with the authenticated API key. Returns: account_id, email_address, is_locked, is_paid_hs, is_paid_hf, quotas, callback_url, role_code, team_id, locale, usage, settings.
- **Dropbox Sign (HelloSign) account bulk update** (Update). Update a Dropbox Sign account, e.g. to change its callback URL or locale. Returns the account object including account_id, email_address, callback_url, locale, quotas, and settings.
- **Create a Dropbox Sign (HelloSign) account create** (Create). Create a new Dropbox Sign (HelloSign) account associated with the specified email address. Returns: account_id, email_address, is_locked, quotas. Required: email_address.
- **Create a Dropbox Sign (HelloSign) account verify** (Create). Verify whether a Dropbox Sign (HelloSign) account exists for a given email address. Returns the matched account's email_address when found. Required: email_address.
- **List all Dropbox Sign (HelloSign) API app lists** (List). List HelloSign API Apps accessible to you, including apps owned by teammates when you hold an Admin or Developer role on your team. Returns: name, client_id, callback_url, domains, is_approved. Max 100 per page.
- **Create a Dropbox Sign (HelloSign) API app** (Create). Create a new HelloSign API App. Returns the created app including its name, domains, client_id, callback_url, and is_approved status. Required: name, domains.
- **Delete a Dropbox Sign (HelloSign) API app by ID** (Delete). Delete a HelloSign API App by its client id. Returns an empty 204 response on success. Can only be invoked for apps you own. Required: id.
- **Get single Dropbox Sign (HelloSign) API app by ID** (Get). Get a HelloSign API App by id (the app's client_id). Returns: name, domains, client_id, callback_url, is_approved. Required: id.
- **Update a Dropbox Sign (HelloSign) API app by ID** (Update). Update an existing HelloSign API App by id (the app's client_id); only the fields you provide are changed, and empty strings clear optional fields. Returns: name, domains, client_id, callback_url, is_approved. Required: id.
- **List all Dropbox Sign (HelloSign) bulk send job lists** (List). List the Bulk Send Jobs you can access in Dropbox Sign (HelloSign). Returns: bulk_send_jobs (each with bulk_send_job_id and signature_request_ids), list_info pagination info, and warnings.
- **Get single Dropbox Sign (HelloSign) bulk send job by ID** (Get). Get a HelloSign Bulk Send Job by id, including the status of its signature requests. Returns: bulk_send_job_id, total, is_creator, created_at. Required: id, bulk_send_job_id.
- **Create a Dropbox Sign (HelloSign) document detect field** (Create). Detect form fields in a PDF document in HelloSign using either PDF form annotations or Dropbox Sign text tags. Returns the detected document object with the detected form-field data. Requires a request body; field definitions follow the upstream DocumentFieldDetectionRequest schema. Required: detection_mode.
- **Create a Dropbox Sign (HelloSign) embedded edit URL** (Create). Get an embedded edit URL for a HelloSign template that can be opened in an iFrame. Returns: edit_url, expires_at. Required: template_id. Only templates created via the embedded template process can be edited with this endpoint.
- **Get single Dropbox Sign (HelloSign) embedded sign URL by ID** (Get). Get an embedded HelloSign sign URL for a signature that can be opened in an iFrame. Returns: sign_url, expires_at. Required: id.
- **Get single Dropbox Sign (HelloSign) fax file by ID** (Get). Download the files associated with a fax in HelloSign. Returns the fax files as a binary PDF (application/pdf) download. fa5c8a0b0f492d768749333ad6fcc214c111e967). Required: id.
- **Dropbox Sign (HelloSign) fax line add users bulk update** (Add). Add a user to a HelloSign fax line. Returns the fax line's number, its list of accounts, and created_at/updated_at timestamps. Required: number.
- **List all Dropbox Sign (HelloSign) fax line area codes** (List). List available HelloSign fax line area codes for a given country, optionally filtered by state, province, or city. Returns: area_codes. Required: country.
- **Create a Dropbox Sign (HelloSign) fax line create** (Create). Purchase a new fax line in HelloSign. Returns the fax line's number, created_at, updated_at, and linked accounts. Required: area_code, country.
- **List all Dropbox Sign (HelloSign) fax line lists** (List). List HelloSign fax lines. Returns the properties and settings of each fax line, including its number, created_at, updated_at, and associated accounts.
- **Dropbox Sign (HelloSign) fax line remove users bulk update** (Delete). Remove a user's access to a fax line in HelloSign. Returns the updated fax line including its number, created_at, updated_at, and accounts. Required: number.
- **Dropbox Sign (HelloSign) fax lines bulk delete** (Delete). Delete a fax line in HelloSign (Dropbox Sign), removing the specified fax line from the subscription. Returns an empty 204 response on success. The fax line to delete is identified in the required JSON request body. Required: number.
- **List all Dropbox Sign (HelloSign) fax lines** (List). Get a HelloSign Fax Line's properties and settings by its number. Returns: number, created_at, updated_at, accounts. Required: number.
- **List all Dropbox Sign (HelloSign) fax lists** (List). List faxes in HelloSign. Returns properties of multiple faxes including fax_id, title, original_title, sender, created_at, and test_mode. Max 100 per page.
- **Create a Dropbox Sign (HelloSign) fax send** (Create). Send a fax in HelloSign with the submitted file(s). Returns: fax_id, title, sender, created_at, transmissions, test_mode. Required: recipient.
- **Delete a Dropbox Sign (HelloSign) fax by ID** (Delete). Delete a HelloSign fax by id, removing the specified fax from the system. Returns an empty 204 response on success. Required: id.
- **Get single Dropbox Sign (HelloSign) fax by ID** (Get). Get a single fax in HelloSign by id. Returns: fax_id, title, subject, message, sender, files_url, created_at, transmissions, test_mode. Required: id.
- **Create a Dropbox Sign (HelloSign) report create** (Create). Create a report in HelloSign. Returns: report, warnings. Required: start_date, end_date, report_type. The report is generated asynchronously and delivered by email as a CSV download link; the requested date range may span up to 12 months and start_date must be no more than 10 years in the past.
- **Create signature request bulk create embedded with template** (Create). Create a HelloSign bulk send job that sends up to 250 signature requests built from the given templates for signing in an embedded iFrame. Returns: bulk_send_job_id, total, is_creator, created_at. Required: template_ids, client_id. Only available on the Standard plan and higher.
- **Create a Dropbox Sign (HelloSign) signature request bulk send with template** (Create). Bulk send up to 250 signature requests based on a HelloSign template. Returns: bulk_send_job_id, total, is_creator, created_at. Required: template_ids. Requires a Standard plan or higher.
- **Create a Dropbox Sign (HelloSign) signature request cancel** (Create). Cancel an incomplete HelloSign signature request by id. Returns an empty 200 OK response on success; cancelation is asynchronous and confirmed via the signature_request_canceled event. The action is not reversible. Required: signature_request_id.
- **Create signature request create embedded with template** (Create). Create an embedded HelloSign signature request from one or more templates to be signed in an embedded iFrame. Returns: signature_request_id, signing_url, title, is_complete, signatures. Required: template_ids, client_id, signers. Embedded requests can only be signed in an iFrame.
- **Create a Dropbox Sign (HelloSign) signature request create embedded** (Create). Create an embedded HelloSign signature request with documents to be signed in an embedded iFrame. Returns: signature_request_id, signing_url, is_complete, signatures, subject, created_at. Required: client_id. Embedded requests can only be signed in an embedded iFrame, not on Dropbox Sign.
- **Update signature request edit embedded with template by ID** (Update). Edit a HelloSign embedded signature request created from one or more templates so it can be signed in an embedded iFrame. Returns the edited signature request object with its updated details. Requires id, template_ids, client_id, and signers. Edit and resend deducts the signature request quota.
- **Update a Dropbox Sign (HelloSign) signature request edit embedded by ID** (Update). Edit an embedded signature request in Dropbox Sign, resubmitting its documents and settings for signing in an embedded iFrame. Returns: signature_request_id, signing_url, title, subject, is_complete, expires_at. Required: id, client_id. Editing and resending deducts the signature request quota.
- **Update a Dropbox Sign (HelloSign) signature request edit with template by ID** (Update). Edit and resend a HelloSign signature request based on the specified templates. Returns the updated signature request including signature_request_id, title, subject, is_complete, custom_fields, and signatures. Requires id, template_ids, and signers. Editing and resending deducts your signature request quota. Required: id, template_ids, signers.
- **Update a Dropbox Sign (HelloSign) signature request edit by ID** (Update). Edit and resend a HelloSign signature request with updated documents, signers, and settings. Returns the updated request including signature_request_id, title, subject, is_complete, and signatures. Required: id. Note that each edit and resend deducts the signature request quota.
- **Get single Dropbox Sign (HelloSign) signature request file by ID** (Get). Download the current documents for a HelloSign signature request. Returns the file contents as binary — a single merged PDF or a ZIP archive of individual documents. Returns 409 while the files are still being prepared. Required: id, signature_request_id.
- **Get single Dropbox Sign (HelloSign) signature request files as data uris by ID** (Get). Download a HelloSign signature request's current documents as a base64-encoded data URI (PDFs only). Returns a JSON object with a single field: data_uri. Returns 409 while files are still being prepared. Required: id.
- **Get single Dropbox Sign (HelloSign) signature request files as file URL by ID** (Get). Get a HelloSign signature request's current documents as a file url by id. Returns: file_url, expires_at. PDFs only; a 409 is returned while the files are still being prepared. Required: id, signature_request_id.
- **List all Dropbox Sign (HelloSign) signature request lists** (List). List HelloSign signature requests you can access, including ones you have sent or received but excluding those you were only CCed on. Returns: signature_request_id, title, subject, requester_email_address, is_complete, created_at, expires_at, and signatures.
- **Create a Dropbox Sign (HelloSign) signature request release hold** (Create). Release a held SignatureRequest in HelloSign, sending the signing requests to all signers. Returns the released SignatureRequest including signature_request_id. Required: signature_request_id. Only applies to requests created from an UnclaimedDraft that was flagged to be held.
- **Create a Dropbox Sign (HelloSign) signature request remind** (Create). Send a reminder email to a signer for a HelloSign signature request. Returns the updated signature request with signature_request_id, title, is_complete, and signatures. Required: signature_request_id, email_address. Reminders cannot be sent within 1 hour of the last reminder and are not supported for embedded signature requests.
- **Create a Dropbox Sign (HelloSign) signature request remove** (Create). Remove your access to a completed HelloSign signature request. The request must be fully executed (signed or declined by all parties); removal is synchronous, immediate, and not reversible. Returns an empty 200 OK response on success. Required: signature_request_id.
- **Create a Dropbox Sign (HelloSign) signature request send with template** (Create). Create and send a new HelloSign signature request based on one or more templates. Returns: signature_request_id, status, metadata. Required: template_ids, signers.
- **Create a Dropbox Sign (HelloSign) signature request send** (Create). Create and send a new HelloSign signature request with the submitted documents. Returns: signature_request_id, title, subject, message, created_at, expires_at, signatures, and metadata. Requires either files or file_urls, and either signers or grouped_signers.
- ...and 22 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
