Connect your AI agent

Give Claude, Cursor or any MCP client the run of GEOboom: connecting, what it may do, and a first session.

Connect Claude, Cursor or any MCP client, and your agent can do in GEOboom what you do in the app: set up projects and campaigns, find prospects, decide them, launch, answer publishers and write deals down. It works through the same operations the app uses, so it sees what you see and is held to the same rules.

Connect

The server is at https://api.geoboom.io/mcp. Add it to your client, sign in to GEOboom when it asks, choose the organisation and what the agent may do, and its tools appear.

Claude Code

claude mcp add --transport http geoboom https://api.geoboom.io/mcp

Then run /mcp, pick geoboom and choose Authenticate. A browser opens to sign in and approve.

Claude

In Settings → Connectors, choose Add custom connector, name it GEOboom and paste https://api.geoboom.io/mcp. Connect, sign in, approve.

Cursor

Add it to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "geoboom": { "url": "https://api.geoboom.io/mcp" }
  }
}

Any other client

The server speaks MCP over Streamable HTTP, without sessions, and signs agents in with OAuth 2.1 (PKCE, client ID metadata documents or dynamic registration). A client that cannot sign in can send an API key instead, made by an owner in Settings → Integrations:

claude mcp add --transport http geoboom https://api.geoboom.io/mcp \
  --header "Authorization: Bearer gbk_..."

What an agent may do

Only an owner of the organisation can approve a connection. They choose what it may do, and sending and spending start unticked:

ScopeAllows
readSee everything: projects, campaigns, prospects, publishers, contacts, deals and the inbox, threads included.
campaigns:writeCreate and change projects and campaigns, set up prospecting, import URLs and decide which fit, edit drafts.
prospecting:spendSpend: run prospecting, set monthly credit budgets, turn on automatic scheduling.
mail:sendReach publishers: reply on threads, send first emails, launch or resume a campaign. Sent email cannot be taken back.
deals:writeWrite deals down: terms, prices, paid, placements and whether they are live.

Some things stay with people in the app, whatever the scopes: inviting and removing members, making or widening keys and connections, deleting projects and campaigns, and billing. Archiving and pausing are allowed; deleting is not.

Sending and spending

A tool that reaches a person outside GEOboom or commits credits takes a required idempotency_key argument. The agent makes one per intended action, a UUID is ideal, and passes the same one if it retries. A retry then gets the first call's answer instead of a second email or a second charge.

GEOboom also checks the thing itself, whatever the key: a reply identical to one sent on the same thread in the last 24 hours is refused, and so is a reply when a message arrived after the one the agent says it read (seenMessageId), so it answers what the publisher actually said.

Some tools ask before they commit: campaigns_resume and drafts_send answer with the cost first when there is one, and go ahead when called again with it agreed. Your client shows which tools only read and which reach outside, and most ask you before running the second kind.

Long work

Prospecting takes minutes. prospecting_run returns at once with a jobId; the agent follows it with jobs_get and reads the run's progress with prospecting_latestRun. The prospects it found are then in prospects_list.

When a tool refuses

A refusal comes back as a tool error whose text says what was wrong in plain words: a missing permission, no credits, something not found in this organisation. The error codes are the same as the API's.

A first session

What an agent does to take a brand from nothing to agreed placements:

  1. org_get: credits available and whether the organisation is activated.
  2. projects_create for the brand, then campaigns_create in it. A campaign starts paused and empty.
  3. prospecting_saveKeywords with the searches the brand's buyers make (or prospecting_savePrompts with the questions they ask AI), prospecting_setMode to make it the campaign's source, and prospecting_run. Or bring your own list with prospects_import.
  4. jobs_get until the run is done, then prospects_list to see the pages found, most valuable first.
  5. prospects_setVerdict to mark the fits, or prospects_planAutoFilter and prospects_autoFilter to let the campaign's rules decide. Fits are searched for contacts.
  6. campaigns_resume to launch: first emails go from the project's mailboxes on their schedule.
  7. threads_list with tab: "need_action" for the replies that need an answer, threads_get to read one, and threads_reply to answer.
  8. When terms are agreed: deals_create, deals_update with the price, deals_addPlacement for what goes where, and deals_updatePlacement to mark it live. GEOboom checks live placements every day; deals_list shows which are still as agreed.

Every tool is listed, with its inputs, in the API reference: each operation there is a tool, named with an underscore (deals.create is deals_create).

Book a demo with Oleksii

30 minutes with GEOboom’s Head of Marketing: your sites, your prospects, live.

Free trial

Request GEOboom free trial

Leave your work email and we’ll get in touch to set your trial up.

Have an account? Sign in