Bombora MCP connector
The Bombora connector brings your intent signals, account lists, and delivery destinations into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so your team can ask which accounts are surging and act on the answer.
- App credentials
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Which accounts show surging intent signals this week?
Working in Bombora with Elaichi
-
List all Bombora signal definitions
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Bombora to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Bombora 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.
Bombora MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
Bombora 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. The plugin directory lives at chatgpt.com/plugins.
Bombora 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.
Bombora MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 Bombora 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.
What teams do with Bombora through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Bombora is logged.
-
Sales
Find out which accounts are surging
Ask which accounts on your target list are showing rising intent this week before you plan outreach. The answer comes from your live Bombora signals, not a stale export.
-
Marketing
Set up a new intent signal
Define a signal around the topics your next campaign covers and point it at the right account list. Adjust it later as the campaign shifts without opening Bombora.
-
Account-Based Marketing
Keep target account lists current
Add newly qualified accounts to a list, retire the ones that closed, and check what is on each list before a launch.
-
Revenue Operations
Route surge data to the right place
Create or update a destination so signals land in the CRM or ad platform where the team already works, and review every destination that is currently receiving data.
-
Demand Generation
Review intent events across campaigns
Pull the events tied to a signal, group them by account, and summarize what changed since the last review.
-
Sales Development
Prioritize the week's call list
Ask for accounts that both sit on your territory list and show intent on your product topics, then get a ranked list to work through.
Try asking
- “Which accounts show surging intent signals this week?”
- “Summarize the account list for enterprise prospects.”
- “Which destinations received signal exports yesterday?”
What connecting Bombora gets you
6 screens from Elaichi, each doing one job for your Bombora account.
Ask Elaichi to work across your apps.
Which accounts show surging intent signals this week?
Summarize the account list for enterprise prospects.
Which destinations received signal exports yesterday?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Bombora questions, get live answers.
Query signal definitions and account lists in plain language, straight from Bombora.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
One endpoint, every mcp client connects.
Claude, chatgpt and cursor reach Bombora through a single governed org endpoint.
ElaichiToolsTool catalog
54 Bombora tools, zero custom code.
Signal definitions, account lists and destinations, all covered without writing a connector.
ElaichiToolboxesToolboxes
Each team gets its own toolbox.
Sales, marketing and ops work from separate Bombora toolboxes scoped to their needs.
ElaichiConnectionsShared connections
Delegate Bombora access without sharing logins.
See who connected each account and how many teams and members use it.
ElaichiAudit logAudit log
Every Bombora call, logged and answerable.
See who ran what against Bombora, when, and on which resource.
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.
Bombora digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch signal definitions
Bombora
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 Jake Morgan
Approve Deny -
Post the digest
Bombora
Queued
Automations
A schedule fires, a person still approves.
Bombora records are fetched, grouped and drafted into a digest before anyone posts back.
Bombora health
Refreshed 4 minutes ago · every 15 minutes · from the signal definitions collection
Signal definitions
1,284 ↓ 12%
Account lists
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Signal definitions created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales NA 27%
Marketing 21%
Revenue Ops 18%
Collections and dashboards
Bombora numbers, computed, not asked for.
Four metrics and a 14 day chart of records created, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Bombora
All three can connect Bombora 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 Bombora tools | Allow or restrict single Bombora 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 Bombora 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.
Bombora tools for your AI agents
54 tools are ready to call through Elaichi's MCP endpoint the moment you connect Bombora, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Bombora to Claude?
Connect Bombora in Elaichi first: you enter the app credentials Bombora issued for your account, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself when Claude asks, and your Bombora signals and account lists are available in the conversation.
Does Bombora work with ChatGPT and Cursor as well as Claude?
Yes. Bombora is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. Each client sees the same Bombora connection with the same restrictions.
What can an AI agent actually do with my Bombora data?
It can list and read your Bombora signal definitions, account lists, destinations, and intent events, and it can create or update them when you ask. In practice that means asking which accounts are surging on a topic, adding accounts to a list, or setting up a destination for surge data. Because Bombora exposes many actions, short concrete asks like 'show my account lists' work better than long paragraphs.
Does connecting Bombora give the AI access to everything in my account?
No. Every call to Bombora runs inside the access of the person who signed in, so the AI sees the signals, lists, and destinations that person already sees. Elaichi can narrow that access further with restrictions, and it never widens it beyond what Bombora itself grants.
Can I stop an agent from deleting or changing things in Bombora?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Bombora signals and account lists while restricting deletion or updates. 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 a Bombora connection when someone leaves?
Offboarding the person in Elaichi ends their access to Bombora at once, across every client they used. A Bombora connection shared with the team keeps working for everyone else. If you disconnect Bombora in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.
Does the Bombora MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Bombora 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 Bombora?
Yes. Both let Claude, ChatGPT or Cursor use Bombora. 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 Bombora call.
How is Elaichi different from Composio for Bombora?
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 Bombora: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Bombora 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