E Signature
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.
-
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.
4 tools
How to connect
How to connect BoloSign to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect BoloSign once
-
Open Connections, choose Add connection, and pick BoloSign.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect BoloSign to 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.
Connect BoloSign to 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.
Connect BoloSign to 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 BoloSign 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 BoloSign through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
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.
-
HR
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.
-
Legal
Turn an approved PDF into a template
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.
-
Operations
Pull intake form answers into one place
Gather the responses from a BoloSign intake or request form and summarize what people asked for, without opening each submission one by one.
-
Finance
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.
-
Customer success
Find every document tied to a customer
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.
Try asking
- “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.”
AI tools
BoloSign tools for your AI agents
4 tools are ready to call through Elaichi's MCP endpoint the moment you connect BoloSign, 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 BoloSign gets you
6 screens from the product, each doing one job for your BoloSign account.
The agent
Ask about documents, get answers from BoloSign.
Three starter prompts pull live documents, templates and form responses in plain language.
- documents
- templates
- respondents
- form responses
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach BoloSign here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
4 BoloSign tools ready without custom code.
The catalog lists every tool, resource and method for documents, templates and respondents.
- List all BoloSign get documents
- Create a BoloSign PDF template lambda
- List all BoloSign get template respondents
- List all BoloSign get form responses
ElaichiToolsToolboxes
Every team gets its own BoloSign toolbox.
Toolboxes are scoped per team, so Legal and Sales see different BoloSign tools.
- Legal
- Sales
- People
- Finance
ElaichiToolboxesShared connections
Teammates send documents without seeing a credential.
The connections table shows who connected each BoloSign account and its shared teams.
- Legal
- Sales EMEA
- People Ops
- Finance
ElaichiConnectionsAudit log
Every BoloSign call is written down.
When, who, what happened, type and resource for each document and template action.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 drafts the signature digest, you approve.
Six steps fetch BoloSign documents, group them, draft a digest, then post it back.
BoloSign digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch documents
BoloSign
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
BoloSign
Queued
Collections and dashboards
BoloSign signature numbers computed, not requested.
Four metrics, 14 days of documents created and a team breakdown, refreshed on schedule.
BoloSign 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
Legal 34%
Sales EMEA 27%
People Ops 21%
Finance 18%
Related connectors
More from the catalog
FAQ
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 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.
Put BoloSign in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.