# E-Signature MCP connectors for Claude, ChatGPT and Cursor 5+ E-Signature connectors in the Elaichi catalog, each callable through https://api.elaichi.ai/mcp once connected, under the same roles, restrictions and audit log as the rest of the catalog. Source: https://elaichi.ai/connectors/category/e-signature/ | | | | --- | --- | | Category | E-Signature | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | ## E-Signature connectors - [BoloSign](https://elaichi.ai/connectors/bolosign/) — 4 tools · hosted sign-in - [Firma](https://elaichi.ai/connectors/firma/) — 48 tools · hosted sign-in - [Ironclad](https://elaichi.ai/connectors/ironclad/) — 13 tools · bring your own OAuth app - [Penneo](https://elaichi.ai/connectors/penneo/) — 22 tools · bring your own OAuth app - [SpotDraft](https://elaichi.ai/connectors/spotdraft/) — 46 tools · hosted sign-in ## What teams do with E-Signature connectors ### Legal - **Keep the NDA template current** (Firma) — 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** (SpotDraft) — 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** (Penneo) — 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** (Ironclad) — 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** (BoloSign) — 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** (Firma) — 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** (Firma) — 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** (Penneo) — 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** (BoloSign) — 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** (Firma) — 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** (Penneo) — 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** (BoloSign) — Before an invoice goes out, check that the order form or engagement letter in BoloSign has been completed by every party named on it. ## Things to ask once it is connected - "Which BoloSign documents are still waiting on respondents?" (BoloSign) - "Which Firma templates changed in the last 30 days?" (Firma) - "Which Ironclad workflows are still awaiting signature this week?" (Ironclad) - "Which Penneo casefiles are still waiting on signatures?" (Penneo) - "List SpotDraft contracts created this month by organization entity." (SpotDraft) ## What an agent can call in E-Signature 133 tools across the category. 3 of these connectors use hosted sign-in with nothing to register first; 2 ask you to bring your own OAuth app. ## 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. ### Whose access does an agent get on a shared E-Signature connection? The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential. ## Related categories - [Cloud Storage](https://elaichi.ai/connectors/category/cloud-storage/) - [Compliance](https://elaichi.ai/connectors/category/compliance/) - [Accounting](https://elaichi.ai/connectors/category/accounting/) [Browse the full connector catalog](https://elaichi.ai/connectors/)