BoloSign MCP connector

Connect BoloSign in Elaichi first, which means pasting an API key from your BoloSign account settings; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Claude can start working with your BoloSign documents, templates, and form responses.

Yes. Once BoloSign is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect BoloSign once and every client you use picks it up.

With BoloSign connected, an agent can list your documents and tell you which are signed and which are still waiting, show who was sent a template and where each of them stands, and read the answers people submitted through your BoloSign forms. It can also take a finished PDF and set it up as a new BoloSign template. It cannot send, sign, or delete documents through this connector.

No. Every request runs as the person who signed in, so the AI only sees the BoloSign documents, templates, and form responses that person can already see in BoloSign itself. Elaichi can narrow that access further, for example by allowing only reading and not template creation, but it can never grant more than the person already has.

Yes. One person connects BoloSign 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 the audit log records exactly who looked at which BoloSign documents or created which template.

Yes. This BoloSign connector cannot delete or edit documents at all, and the one action that changes anything, creating a PDF template, can be switched off per team or per person in Elaichi. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it.

When you offboard someone in Elaichi, their access to BoloSign through every connected client ends at once. If they had shared a BoloSign connection with the team, it keeps working for everyone else. If you want BoloSign gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Yes. BoloSign 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.

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

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