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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect SignWell to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SignWell once
-
Open Connections, choose Add connection, and pick SignWell.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
SignWell MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect SignWell to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with SignWell through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Send the order form before the call ends
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.
-
HR
Run a batch of offer letters from a spreadsheet
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.
-
Legal
Keep the NDA template current
Update the standard NDA template in SignWell when wording changes, so everyone sends the approved version from then on.
-
Finance
Chase unsigned vendor agreements
Ask for a reminder to go to anyone who has not signed a vendor agreement yet, instead of hunting down each one by hand.
-
Operations
File the completed PDF where it belongs
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.
-
Customer success
Fix a recipient after the document went out
When a customer asks for a different signer, swap the recipient on the SignWell document rather than cancelling and starting over.
Try asking
- “Send the NDA template to [email protected] 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.”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
SignWell tools for your AI agents
26 tools are ready to call through Elaichi's MCP endpoint the moment you connect SignWell, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting SignWell gets you
6 screens from the product, each doing one job for your SignWell account.
The agent
Ask about SignWell documents in plain language.
Send, remind, and pull completed PDFs by asking, with answers from live SignWell records.
- documents
- templates
- bulk sends
- recipients
Ask Elaichi to work across your apps.
Send the NDA template to [email protected] 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.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings SignWell to every client.
Claude, ChatGPT and Cursor reach SignWell through one governed endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
26 SignWell tools, ready without writing code.
Documents, templates, bulk sends, reminders and hooks, cataloged and callable with no custom code.
- Create a SignWell document
- Get single SignWell document by ID
- Delete a SignWell document by ID
- SignWell documents send
Toolboxes
Every team gets its own SignWell toolbox.
Sales sends from templates, HR runs bulk sends, each team scoped to its own work.
- Sales
- HR
- Legal
- Finance
Shared connections
Share one SignWell connection, never the key.
Teammates send and track documents through a shared connection without ever seeing the API key.
- Sales EMEA
- Sales US
- HR
- Legal
Audit log
Every SignWell action is logged with a name.
Who sent, reminded or deleted which document, recorded when it happened and kept for good.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs SignWell follow-up end to end.
Documents awaiting signature are fetched, grouped and digested, a person approves, reminders go out.
SignWell digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch documents
SignWell
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
SignWell
Queued
Collections and dashboards
SignWell health, computed on a schedule, no prompt.
Documents created over 14 days, completion metrics and a team breakdown, refreshed without a model.
SignWell health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Templates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
HR 21%
Legal 18%
Related connectors
More from the catalog
FAQ
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 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.
Put SignWell in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.