Skip to content

Autobound MCP connector

The Autobound connector brings companies, contacts, buyer signals, and personalized outreach content into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so each person can research an account and draft a tailored message inside their own Autobound access.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which Autobound signals hit my accounts this week?

Working in Autobound with Elaichi

  • Get single Autobound account by ID
  • Get single Autobound credit by ID
  • Get single Autobound company by ID
Ask anything…
Governance / Audit log Last 24 hours
Autobound Get single Autobound company by ID Emily Carter · Claude · 9:41 AM Done
Autobound Get single Autobound credit by ID Emily Carter · Claude · 9:41 AM Done
Autobound Get single Autobound account by ID Emily Carter · Claude · 9:41 AM Done
Autobound Autobound companies bulk create Megan Brooks · ChatGPT · 9:38 AM Done
Autobound Create a Autobound company Ryan Hayes · Cursor · 9:35 AM Done

How to connect Autobound to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Autobound MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Autobound MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Autobound MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Autobound MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Autobound to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Autobound through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Autobound is logged.

  • 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.”

See all 35 Autobound tools →

What connecting Autobound gets you

6 screens from Elaichi, each doing one job for your Autobound account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about Autobound accounts in plain language.

Three starter prompts pull answers from live companies, contacts and signals.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Autobound.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Get single Autobound account by ID Get Get the authenticated Autobound account's details. Returns: id and account-specific attributes; the full field breakdown depends on the account's configuration — consult the Autobound API docs for the field-level schema.
Get single Autobound credit by ID Get Get the current running credit balance for the Autobound workspace. Returns: balance, used, granted, and since. This endpoint is free and consumes no credits.
Get single Autobound company by ID Get Enrich a single company in Autobound with signal data via POST /v1/companies/enrich. Returns enriched company signal data; the specific request body and response fields are not enumerated in the available source documentation for this endpoint — consult the Autobound API docs for the full schema.
Autobound companies bulk create Create Bulk-enrich companies in Autobound with signal data via POST /v1/companies/bulk. Returns bulk enrichment results; the specific request body and response fields are not enumerated in the available source documentation for this endpoint — consult the Autobound API docs for the full schema.
Create a Autobound company Create Enrich a company in Autobound with signal data via POST /v1/companies/enrich. Returns enriched company signal data; the specific request body and response fields are not enumerated in the available source documentation for this endpoint — consult the Autobound API docs for the full schema.

Tool catalog

35 Autobound tools ready on connect.

Companies, contacts, signals, credits and timelines, with no custom code to write.

ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Autobound · accounts and contacts

Autobound starter 18 Mar 4, 2026

Sales development toolbox

Autobound · signals and outreach lists

— 9 Mar 2, 2026

Marketing toolbox

Autobound · companies and segments

— 24 Feb 27, 2026

Revenue operations toolbox

Autobound · bulk imports and credits

Autobound starter 6 Feb 19, 2026

Customer success toolbox

Autobound · account timelines

— 31 Jan 30, 2026

Partnerships toolbox

Autobound · company research

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Autobound toolbox.

Curate one toolbox per team and scope Autobound access to that team.

ElaichiConnections
Connection Scope Status Access
AU

Autobound (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AU

Autobound (Sales AMER)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AU

Autobound (Sales development)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AU

Autobound (Marketing)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
AU

Autobound (Revenue operations)

Connected by Ryan Hayes

Personal • Active Not shared
AU

Autobound (Customer success)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share an Autobound account, never a credential.

See who connected each account and how many teams and members use it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Autobound Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Autobound Companies Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Autobound Companies List Toolbox

Audit log

Every Autobound call is on the record.

When, who, what happened, type and resource, in an append only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Autobound digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch companies

    Autobound

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Autobound

    Queued

Automations

A schedule drafts your Autobound signal digest.

Six steps fetch signals, group them, draft a digest, then post after approval.

Autobound health

Refreshed 4 minutes ago · every 15 minutes · from the companies collection

Live

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%

Collections and dashboards

Autobound numbers computed, not asked for.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Autobound, by what to check
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 Free for one person; $15 per user per month on Gold. 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.

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.

Questions, answered

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, Microsoft Copilot, 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 my team share one Autobound connection?

Yes. One person connects Autobound with an API key in Elaichi and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so every draft, search, or export in Autobound is logged under the name of the person who did it.

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 restricting creating companies, deleting webhooks, or spending credits on exports. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot