# SignWell MCP connector

The SignWell connector lets Claude, ChatGPT, Cursor and the Elaichi Agent create, send, remind and retrieve SignWell documents, templates and bulk sends, with each person acting under their own access and every action logged.

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

## Facts

| | |
| --- | --- |
| Application | SignWell |
| Category | E-Signature |
| AI tools | 26 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, 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 SignWell is connected

- Send the NDA template to dana@acme.com and set a reminder.
- Create a bulk send from this CSV using the offer letter template.
- Get the completed PDF for the Acme master services agreement.

## Connect SignWell in Elaichi

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

1. Open Connections, choose Add connection, and pick SignWell.
2. Optionally set Share with, then press Connect.
3. Paste a SignWell API key. One person generates a token in SignWell 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 SignWell tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## SignWell 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.

## SignWell 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`.

## SignWell 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 today. The plugin directory lives at chatgpt.com/plugins.

## SignWell 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.

## Connect SignWell 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 data and remove access", which you tick yourself. Calling a SignWell tool needs "Run your connected tools". 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 Delete, which reaches into connected apps and cannot be undone.

## What teams do with SignWell through Elaichi

### Send the order form before the call ends

Sales. Ask for the order form template to go to the buyer with their name and email filled in, then check whether it has been signed before the follow-up.

### Run a batch of offer letters from a spreadsheet

HR. Hand over the CSV of new hires, have it checked for errors, and send every offer letter from the same SignWell template in one bulk send.

### Keep the NDA template current

Legal. Update the standard NDA template in SignWell when wording changes, so everyone sends the approved version from then on.

### Chase unsigned vendor agreements

Finance. Ask for a reminder to go to anyone who has not signed a vendor agreement yet, instead of hunting down each one by hand.

### File the completed PDF where it belongs

Operations. Once a document is fully signed, pull the completed PDF from SignWell so it can be attached to the record or sent to the counterparty.

### Fix a recipient after the document went out

Customer success. When a customer asks for a different signer, swap the recipient on the SignWell document rather than cancelling and starting over.

## Elaichi vs Zapier MCP vs Composio for SignWell

All three can connect SignWell 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 SignWell tools | Allow or restrict single SignWell 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 SignWell 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 | $15 per user per month. | 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 SignWell to Claude?

Connect SignWell in Elaichi by pasting in a SignWell API key, which takes a minute and needs no OAuth application, client ID or secret. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and SignWell is available in Claude.

### Does SignWell work with ChatGPT and Cursor as well as Claude?

Yes. SignWell is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. There is nothing extra to set up per client.

### What can an AI agent actually do with my SignWell data?

An agent can create a SignWell document from a template, send it to the right people, change a recipient, send a reminder to anyone who has not signed, and fetch the completed PDF once everyone has. It can also run bulk sends from a CSV of names and emails and check that file for errors first. Short, concrete asks such as send the NDA to this email work better than long paragraphs.

### Does connecting SignWell give the AI everything in my SignWell account?

The connection runs under the SignWell API key that was connected, so an agent can only reach what that key can reach, and nothing in Elaichi widens it. Elaichi can narrow it further, for example by taking deleting documents or templates out of what a team is allowed to do. Access only ever gets smaller from here, never bigger.

### Can my team share one SignWell connection?

Yes. One person connects SignWell in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every document sent or reminder issued is logged with that person's name.

### Can I stop an agent from deleting or changing things in SignWell?

Yes. Restrictions in Elaichi work per action, so deleting a SignWell document, deleting a template or changing recipients can each be switched off for a team. A restricted action is left out of the tool list the AI client sees, so it cannot be called no matter how the prompt is worded.

### What happens to a SignWell connection when someone leaves?

Offboarding a person in Elaichi ends their access to SignWell through every client at once. If they were using a shared SignWell connection, it keeps working for everyone else on the team. Disconnecting SignWell in Elaichi removes it from Claude, ChatGPT, Cursor and every other client in one step.

### Does the SignWell MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. SignWell 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, 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 SignWell?

Yes. Both let Claude, ChatGPT or Cursor use SignWell. 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 SignWell call.

### How is Elaichi different from Composio for SignWell?

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 SignWell: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 26 SignWell tools

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

- **Create a SignWell document** (Create). Create a SignWell document and optionally send it for signing; recipients are notified by email, SMS, or both based on delivery_method. Returns: cfr_part11, test_mode, id, name, subject, and 37 more. Requires files and recipients; set expires_in to 365 or less and provide phone_number in E.164 format for SMS recipients. Required: files, recipients.
- **Get single SignWell document by ID** (Get). Get a SignWell document with all associated data by id; supply the unique document ID from a creation request or Document page URL. Returns: cfr_part11, cfr_part11_signing_mode, test_mode, id, name, subject, message, metadata, created_at, updated_at, recipients, status, files, fields, allow_decline, allow_reassign, and 26 more. Required: id.
- **Delete a SignWell document by ID** (Delete). Delete a SignWell document by id; deleting also cancels document signing if it is in progress. Returns an empty 204 response on success. Required: id.
- **SignWell documents send** (Send). Update a draft SignWell document and send it to its recipients for signing. Returns: cfr_part11, test_mode, id, subject, message, updated_at, recipients, status, files, fields, allow_decline, allow_reassign, and 30 more. subject and message apply to email notifications only; SMS notifications use fixed system templates. Required: document_id.
- **Create a SignWell document templates document** (Create). Create a SignWell document from one or more templates and optionally send it for signature; pre-signed template signatures and initials copy over as visible content without generating signing events. Returns: cfr_part11, cfr_part11_signing_mode, test_mode, id, template_ids, name, recipients, status, files, fields, and 32 more. Required: recipients.
- **SignWell document recipients bulk update** (Update). Update one or more recipients on a sent SignWell document; only recipients who have not started signing can be changed, and only while the document is in sent, viewed, pending, or bounced status. Returns the updated document with id, status, and its recipients (id, name, email, signing_url). Required: document_id, recipients.
- **SignWell document authentications bulk update** (Update). Update passcode delivery settings for recipients on a sent SignWell document; only recipients who have not started signing can be updated. Returns the updated document object including id, status, recipients, and updated_at. Required: document_id, recipients.
- **Create a SignWell document remind** (Create). Send a reminder to SignWell document recipients who have not signed yet, delivered via each recipient's method (email, SMS, or both). Returns the updated document object including id, status, recipients with signing_url, and subject. Required: document_id.
- **Get single SignWell document completed PDF by ID** (Get). Download the completed PDF or ZIP file for a signed Signwell document. Returns file_url in a JSON object when url_only=true, otherwise streams the raw PDF or ZIP binary. zip is unavailable on 21 CFR Part 11 documents. Required: id.
- **Create a SignWell document template** (Create). Create a new reusable SignWell document template. Returns the created template including id, name, status, created_at, fields, placeholders, and files. Each entry in files must supply exactly one of file_url or file_base64; at least one placeholder should be left unassigned. Required: files, placeholders.
- **Get single SignWell document template by ID** (Get). Get a SignWell document template by id, including all associated template data. Returns: id, api_application_id, requester_email_address, custom_requester_name, custom_requester_email, name, subject, message, metadata, created_at, updated_at, placeholders, copied_placeholders, status, reminders, archived, files, fields, and 13 more. Required: id.
- **Update a SignWell document template by ID** (Update). Update an existing SignWell document template by id. Returns the updated template including id, name, status, fields, placeholders, and updated_at. Required: id.
- **Delete a SignWell document template by ID** (Delete). Delete a SignWell document template by id. Returns an empty 204 response on success. Required: id.
- **Get single SignWell API application by ID** (Get). Get a specific SignWell API Application by id. Returns: id, name, callback_urls, created_at, updated_at, owner, preferences. Required: id.
- **Delete a SignWell API application by ID** (Delete). Delete a SignWell API Application by id. Returns an empty 204 response on success. Required: id.
- **List all SignWell hooks** (List). List all webhooks registered in your SignWell account. Returns: id, callback_url, api_application_id.
- **Create a SignWell hook** (Create). Register a SignWell webhook to receive document lifecycle events at a callback URL. Returns the created webhook with id, callback_url, and api_application_id. Required: callback_url. A document_signed event is not emitted when a pre-signed template signature/initials was merely copied as document content.
- **Delete a SignWell hook by ID** (Delete). Delete a registered SignWell webhook by id so document events stop being posted to its callback URL. Returns an empty 204 response on success. Required: id.
- **List all SignWell me** (List). Retrieve the SignWell account information associated with the authenticated API key, including the credential record, user, account, workspace, and contact. Returns: id, role, archived, user, account, workspace, contact. Takes no parameters.
- **Get single SignWell bulk send by ID** (Get). Get a SignWell bulk send by id. Returns: id, name, api_application_id, documents_count, documents_completed, documents_not_completed, created_at, user_id, status, templates. Required: id.
- **List all SignWell bulk sends** (List). List SignWell bulk sends. Returns: id, name, api_application_id, documents_count, documents_completed, documents_not_completed, created_at, user_id, status, template_ids. Optional filters: user_email, api_application_id.
- **Create a SignWell bulk send** (Create). Create a SignWell bulk send that sends a template to multiple recipients from CSV data; the CSV is validated before the send is enqueued (invalid rows return a 422). Returns: id, template_ids, api_application_id, documents_count, created_at, user_id, status. Required: template_ids, bulk_send_csv.
- **List all SignWell bulk sends CSV templates** (List). Get the SignWell Bulk Send CSV template for one or more document templates: a blank CSV whose columns hold the required and optional recipient data for a bulk send, named [placeholder]_[field label] (e.g. signer_company_name). Returns the base64-encoded CSV in data. Required: template_ids[].
- **Create a SignWell bulk sends validate CSV** (Create). Validate a SignWell bulk send CSV, checking its structure and row data before creating the bulk send. Returns the validated CSV configuration with defaults applied: bulk_send_csv, template_ids, skip_row_errors, name, subject, message. Invalid CSVs return 422 row-level errors. Required: template_ids, bulk_send_csv.
- **List all SignWell bulk send documents** (List). List the SignWell documents generated for a bulk send. Returns each document's id, name, status, recipients, files, and created_at. Required: bulk_send_id.
- **Get single SignWell document nom 151 certificate by ID** (Get). Download the NOM-151 certificate for a completed SignWell document by id. By default returns the certificate ZIP file; with url_only=true returns JSON with file_url; with object_only=true returns the raw constancia certificate object as JSON. Required: id. Only succeeds when a NOM-151 certificate is available for the document.