Skip to content

Sales Intelligence

Bombora MCP connector

The Bombora connector brings your intent signals, account lists, and delivery destinations into Claude, ChatGPT, Cursor, and any MCP client, so your team can ask which accounts are surging and act on the answer.

  • How it connects. App credentials. 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.

How to connect

How to connect Bombora to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Bombora once

  1. Open Connections, choose Add connection, and pick Bombora.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste your Bombora app credentials. Bombora authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

bombora
Bombora
1Password
360learning
7shifts
Acquire
Ada
2

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 Bombora to 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.

Connect Bombora to 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 today. The plugin directory lives at chatgpt.com/plugins.

Connect Bombora to 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.

Connect Bombora 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.

Use cases

What teams do with Bombora through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

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

See all 54 Bombora tools below

AI tools

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.

See it in Elaichi

What connecting Bombora gets you

6 screens from the product, each doing one job for your Bombora account.

The agent

Ask Bombora questions, get live answers.

Query signal definitions and account lists in plain language, straight from Bombora.

  • signal definitions
  • account lists
  • destinations
  • topics

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 or Cursor

MCP clients

One endpoint, every mcp client connects.

Claude, chatgpt and cursor reach Bombora through a single governed org endpoint.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

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

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

54 Bombora tools, zero custom code.

Signal definitions, account lists and destinations, all covered without writing a connector.

  • List all Bombora signal definitions
  • Get single Bombora signal definition by ID
  • Create a Bombora signal definition
  • Update a Bombora signal definition by ID
ElaichiTools
Tool Action Description
List all Bombora signal definitions List List all Bombora signal definitions. Returns: signalDefinitionId, status, topicCount, createdDate, modifiedDate, metadata.
Get single Bombora signal definition by ID Get Get a single Bombora signal definition by id. Returns the full signal definition including signalDefinitionId, status, topicCount, createdDate, modifiedDate, metadata, and topics. Required: id.
Create a Bombora signal definition Create Create a new Bombora signal definition from product data points such as domain, keywords, and urls. Returns: signalDefinitionId. Required: metadata.
Update a Bombora signal definition by ID Update Replace a Bombora signal definition by id with new topics and metadata. Returns: metadata, topics. Required: id.
Delete a Bombora signal definition by ID Delete Delete a Bombora signal definition by id. Returns an empty 200 response on success. Required: id.

Toolboxes

Each team gets its own toolbox.

Sales, marketing and ops work from separate Bombora toolboxes scoped to their needs.

  • Sales
  • Marketing
  • Revenue operations
  • Demand generation
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Bombora · account lists and intent signals

Bombora starter 18 Mar 4, 2026

Marketing toolbox

Bombora · destinations and campaign targeting

9 Mar 2, 2026

Revenue operations toolbox

Bombora · signal definitions and data hygiene

24 Feb 27, 2026

Demand generation toolbox

Bombora · surging topics and account scoring

Bombora starter 6 Feb 19, 2026

Customer success toolbox

Bombora · expansion accounts and intent trends

31 Jan 30, 2026

Analytics toolbox

Bombora · signal exports and reporting destinations

12 Jan 22, 2026

Shared connections

Delegate Bombora access without sharing logins.

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

  • Sales EMEA
  • Sales NA
  • Marketing
  • Revenue Ops
ElaichiConnections
Connection Scope Status Access
BO

Bombora (Sales EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
BO

Bombora (Sales NA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
BO

Bombora (Marketing)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
BO

Bombora (Revenue Ops)

Connected by Daniel Ortega

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

Bombora (Demand Gen)

Connected by Clara Nowak

Personal • Active Not shared
BO

Bombora (Customer Success)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Bombora call, logged and answerable.

See who ran what against Bombora, when, and on which resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Bombora Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Bombora Signal definitions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Bombora Signal definitions List Toolbox

Launching 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 fires, a person still approves.

Bombora records are fetched, grouped and drafted into a digest before anyone posts back.

Bombora digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch signal definitions

    Bombora

    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 Michael Brennan

    Approve
  6. Post the digest

    Bombora

    Queued

Collections and dashboards

Bombora numbers, computed, not asked for.

Four metrics and a 14 day chart of records created, refreshed on a schedule.

Bombora health

Refreshed 4 minutes ago · every 15 minutes · from the signal definitions collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Bombora connection?

Yes. One person connects Bombora in Elaichi and shares the connection with a team, and nobody else ever handles the Bombora credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Bombora call.

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 blocking deletion or updates. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

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, and every other client in one step.

Put Bombora in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.