Connectors / E-Signature
E-Signature MCP connectors for Claude, ChatGPT and Cursor
5+ E-Signature connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
E-Signature connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
5 connectors
-
BoloSign Hosted sign-in 4 tools
-
Firma Hosted sign-in 48 tools
-
Ironclad Bring your own OAuth app 13 tools
-
Penneo Bring your own OAuth app 22 tools
-
SpotDraft Hosted sign-in 46 tools
No E-Signature connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with E-Signature connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Legal
-
Keep the NDA template current
Update the standard NDA in Firma, duplicate it for a regional variant, and check which fields and signers each version expects. Retire old templates so nobody sends them by mistake.
-
Start a contract from the approved template
Ask for a new SpotDraft contract from the right template and the right counterparty entity, with the key terms filled in from your notes, without opening a blank form.
-
Open a casefile for a new agreement
Ask for a Penneo casefile to be created for a supplier agreement or NDA, then check which files it holds before anyone is asked to sign.
Sales
-
Kick off an NDA right after the call
Ask for a new NDA or order form workflow for the prospect you just spoke to, filled in from what Ironclad already needs for that contract type, without opening Ironclad yourself.
-
Check which contracts are still unsigned
Ask which quotes and agreements sent through BoloSign this week are still waiting on a signature, and who is holding them up, before the pipeline call.
-
Send the contract before the call ends
Pick the right Firma template, fill in the customer's details and send the signing request while the deal is still warm. The rep never leaves the conversation to do it.
HR
-
Get offer letters out the same day
Create a signing request from the offer letter template, drop in the candidate's name, title and start date, and send it. Cancel and reissue if the terms change before they sign.
-
Build and publish an onboarding form
Draft an onboarding form in Penneo from a description of the fields you need, publish the version, and send a form request to each new starter.
-
Track offer letter and onboarding signatures
See which new hires have signed their offer letter, policy acknowledgment, and tax forms in BoloSign, and who still needs a nudge before their start date.
Finance
-
Track vendor agreements through to signature
List the signing requests tied to a supplier onboarding, check where each one stands, and cancel any that were sent against the wrong terms. Reminder settings on each template are visible too.
-
Check answers on signed casefiles
Ask which casefile answers came back for an approval or expense form in Penneo, and get a clean list rather than clicking through each one.
-
Confirm signed agreements before invoicing
Before an invoice goes out, check that the order form or engagement letter in BoloSign has been completed by every party named on it.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the E-Signature account you connected.
-
Which BoloSign documents are still waiting on respondents?
-
Which Firma templates changed in the last 30 days?
-
Which Ironclad workflows are still awaiting signature this week?
-
Which Penneo casefiles are still waiting on signatures?
-
List SpotDraft contracts created this month by organization entity.
The tools
What an agent can call in E-Signature
- Connectors
- 5+
- Tools
- 133
- Hosted sign-in
- 3
in the E-Signature catalog
callable the moment you connect
connect with nothing to register
Of those 133 tools, 6% delete something. Restricting an agent to reads is not a promise here, it is 63 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 47%
- 63 tools · list, get, search
- Write 41%
- 54 tools · create, update, send
- Delete 6%
- 8 tools · delete, remove, archive
- Other 6%
- 8 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every E-Signature connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.
FAQ
Frequently asked questions
How many E-Signature connectors does Elaichi have?
5+ E-Signature connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use E-Signature connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a E-Signature account once makes it reachable from every one of them.
Do E-Signature connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. E-Signature connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do E-Signature connectors need me to bring my own OAuth app?
Most do not. 3 of the E-Signature connectors use Elaichi's hosted sign-in, with nothing to register. The other 2 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.
Can I stop an agent from writing to E-Signature tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a E-Signature connector is a matter of allowing the reads and leaving the writes out.
Nearby
Teams that connect E-Signature usually connect these too
Put E-Signature connectors in front of your team
14 days on Gold, no credit card. Connect one 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.