Autobound MCP connector
The Autobound connector brings companies, contacts, buyer signals, and personalized outreach content into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can research an account and draft a tailored message inside their own Autobound 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.
35 tools
How to connect
How to connect Autobound to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Autobound once
-
Open Connections, choose Add connection, and pick Autobound.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Autobound API key. One person generates a token in Autobound 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.
Autobound MCP connector for 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.
Autobound MCP connector for 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.
Autobound MCP connector for 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 Autobound 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 Autobound through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Draft a personalized email before the call
Ask for personalized content for a contact and get an opener built from that person's recent signals, ready to paste into your sequence.
-
Sales Development
Find accounts that just showed intent
Search Autobound signals for funding rounds, hiring spikes, or leadership changes across your target list, then pull the matching companies and contacts in one go.
-
Marketing
Load a campaign list into Autobound
Hand over a list of companies and contacts from an event or webinar and have them created in bulk so the team can start personalizing straight away.
-
Account Management
Catch up on a customer's timeline
Pull a company or contact timeline to see what has happened at the account since your last touchpoint before a renewal conversation.
-
Revenue Operations
Keep an eye on credit spend
Check remaining credits and what each type of request costs so nobody is surprised at the end of the month.
-
Sales Leadership
Export buyer intent for the pipeline review
Create a buyer intent export across your accounts and summarize which segments are heating up before the weekly pipeline meeting.
Try asking
- “Which Autobound signals hit my accounts this week?”
- “Summarize the timeline for this Autobound company.”
- “List Autobound contacts added at accounts with new signals.”
Compare
Elaichi vs Zapier MCP vs Composio for Autobound
All three can connect Autobound to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Autobound tools | Allow or restrict single Autobound tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Autobound call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Autobound tools for your AI agents
35 tools are ready to call through Elaichi's MCP endpoint the moment you connect Autobound, 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 Autobound gets you
6 screens from the product, each doing one job for your Autobound account.
The agent
Ask about Autobound accounts in plain language.
Three starter prompts pull answers from live companies, contacts and signals.
- companies
- contacts
- signals
- timelines
Ask Elaichi to work across your apps.
Which Autobound signals hit my accounts this week?
Summarize the timeline for this Autobound company.
List Autobound contacts added at accounts with new signals.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Autobound.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
35 Autobound tools ready on connect.
Companies, contacts, signals, credits and timelines, with no custom code to write.
- Get single Autobound account by ID
- Get single Autobound credit by ID
- Get single Autobound company by ID
- Autobound companies bulk create
ElaichiToolsToolboxes
Every team gets its own Autobound toolbox.
Curate one toolbox per team and scope Autobound access to that team.
- Sales
- Sales development
- Marketing
- Revenue operations
ElaichiToolboxesShared connections
Share an Autobound account, never a credential.
See who connected each account and how many teams and members use it.
- Sales EMEA
- Sales AMER
- Sales development
- Marketing
ElaichiConnectionsAudit log
Every Autobound call is on the record.
When, who, what happened, type and resource, in an append only log.
- 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 your Autobound signal digest.
Six steps fetch signals, group them, draft a digest, then post after approval.
Autobound digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch companies
Autobound
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
Autobound
Queued
Collections and dashboards
Autobound numbers computed, not asked for.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Autobound health
Refreshed 4 minutes ago · every 15 minutes · from the companies collection
Companies
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Companies created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales AMER 27%
Sales development 21%
Marketing 18%
FAQ
Frequently asked questions
How do I connect Autobound to Claude?
Connect Autobound in Elaichi first: pick Autobound from the catalog and paste in an API key from your Autobound settings, since that is how Autobound signs in. 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 https://api.elaichi.ai/mcp as the endpoint. Claude will ask you to sign in to Elaichi as yourself, and Autobound is ready to use.
Does Autobound work with ChatGPT and Cursor as well as Claude?
Yes. Once Autobound 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 Autobound once and every client you use picks it up.
What can an AI agent actually do with my Autobound data?
With Autobound connected, an agent can look up a company or contact, read its timeline, search signals like funding, hiring, or new executives, and draft personalized outreach content for a specific person. It can also add companies and contacts in bulk, create a buyer intent export, and tell you how many credits you have left and what each request costs. Because Autobound has a large set of actions, short concrete asks such as "find signals for Acme this month" work better than long instructions.
Does connecting Autobound give the AI everything in my workspace?
No. Every request to Autobound runs as the person who signed in, so the AI sees only the companies, contacts, signals, and credits that person can already see in Autobound. Elaichi can narrow that further with roles and restrictions, but it can never grant more than the person's own Autobound access.
Can I stop an agent from deleting or changing things in Autobound?
Yes. In Elaichi you can restrict Autobound action by action, for example allowing searches and drafts while blocking creating companies, deleting webhooks, or spending credits on exports. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to an Autobound connection when someone leaves?
When you offboard a person in Elaichi, their access to Autobound through every client ends at once. If they had connected a shared Autobound account, it keeps working for everyone else on the team. Disconnecting Autobound once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Autobound MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Autobound 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.
Is Elaichi an alternative to Zapier MCP for Autobound?
Yes. Both let Claude, ChatGPT or Cursor use Autobound. 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 Autobound call.
How is Elaichi different from Composio for Autobound?
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 Autobound: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Autobound in front of your team
14 days on Gold, no credit card. Connect it once 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.