# BoloSign MCP connector The BoloSign connector lets Claude, ChatGPT, Cursor, or any MCP client see your BoloSign documents, form responses, and who has signed each template, and create new PDF templates, with each person acting under their own BoloSign access. Source: https://elaichi.ai/connectors/bolosign/ ## Facts | | | | --- | --- | | Application | BoloSign | | Category | E Signature | | AI tools | 4 | | Authentication | Connects with an API key | | Needs 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 | Yes | ## What you can ask once BoloSign is connected - Which BoloSign documents are still waiting on respondents? - Summarize this week's BoloSign form responses by template. - List BoloSign templates with the most signed documents. ## Connect BoloSign in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick BoloSign. 2. Optionally set Share with, then press Connect. 3. Paste a BoloSign API key. One person generates a token in BoloSign 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 BoloSign tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect BoloSign to 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. ## Connect BoloSign to 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. ## Connect BoloSign to 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 BoloSign 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 Only Read is granted by default, which is not enough to call a BoloSign tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with BoloSign through Elaichi ### Check which contracts are still unsigned Sales. 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. ### Track offer letter and onboarding signatures HR. 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. ### Turn an approved PDF into a template Legal. Hand over the final version of an NDA or vendor agreement and have it set up as a reusable BoloSign template, ready for the team to send. ### Pull intake form answers into one place Operations. Gather the responses from a BoloSign intake or request form and summarize what people asked for, without opening each submission one by one. ### Confirm signed agreements before invoicing Finance. Before an invoice goes out, check that the order form or engagement letter in BoloSign has been completed by every party named on it. ### Find every document tied to a customer Customer success. List the agreements, renewals, and amendments a customer has in BoloSign, and see which are complete, so the account review starts with the full picture. ## Frequently asked questions ### How do I connect BoloSign to Claude? 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. ### Does BoloSign work with ChatGPT and Cursor as well as Claude? 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. ### What can an AI agent actually do with my BoloSign data? 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. ### Does connecting BoloSign give the AI access to every document in my account? 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. ### Can my team share one BoloSign connection? 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. ### Can I stop an agent from deleting or changing things in BoloSign? 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. ### What happens to a BoloSign connection when someone leaves? 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. ## All 4 BoloSign tools Every tool below is callable through https://api.elaichi.ai/mcp once BoloSign is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all BoloSign get documents** (List). List BoloSign signature documents with optional filtering by search query, date range, document ID, and sort order. Returns: documentId, name, createdAt, status, documentName, documentUrl, authorEmail, finishedPdfUrl, isSigningOrder, signers. Optional filters: query, sortOrder, sortBy, documentId, dateFrom, dateTo, filter. - **Create a BoloSign PDF template lambda** (Create). Send a BoloSign PDF or form template for signing with custom variables and receiver information. Returns: documentId, documentName, documentUrl, authorEmail, signers. The PDF_TEMPLATE variant also supports optional customVariables, mailData, and pdfData. - **List all BoloSign get template respondents** (List). List template respondents in BoloSign, or retrieve a specific respondent by providing respondentDocumentId. Returns: documentId, documentName, documentUrl, authorEmail, finishedPdfUrl, isSigningOrder, signers. - **List all BoloSign get form responses** (List). List BoloSign form responses with optional filtering and pagination. Returns: formResponseId, formId, formTitle, finishedPdfUrl, respondentEmail, response.