Skip to main content
Boom works with any AI tool that supports MCP (Model Context Protocol), like Claude, Cursor, and VS Code. Once it’s connected, the tool can look up and update your customer data for you. It takes two steps, and there’s no API key to set up.
1

Add Boom to your tool

Copy this link:
Then add it the way your tool expects:
Run this in your terminal:
2

Sign in

The first time you use it, a window opens to sign in to Boom, the same login you use for the dashboard. Approve it, and you’re connected.
  • Everything stays inside your organization.
  • In more than one organization? Pick which one when you sign in.
  • There’s no key to copy or keep safe. Access follows your login.

​
What you can do

Once connected, the AI tool gets the same capabilities as the REST API (see one uniform surface):
  • Customer data: find, add, and update people; record and read events (like a purchase or a sign-up); manage custom objects, things like orders or loans; and link records with relationships.
  • Segments: the full authoring loop: discover what’s filterable, validate and preview a filter, create or update an audience, trigger an evaluation, and page through who’s in it.
  • Initiatives: create and configure an initiative, whatever the job it runs, link the templates it sends, drive the lifecycle (launch, cancel, archive, unarchive), and read a summary of the data collected.
  • Participants: add people to an active initiative, list them, check one participant’s status, read conversation transcripts (one participant at a time, or every conversation in pages of up to 100), and stop their outreach.
  • Journeys: the full authoring loop, not just reading: open a draft, add and connect nodes, set the trigger, validate, and publish. Catalogs tell an agent which nodes, conditions, events, templates and variables exist, so it can build a flow without guessing. See journeys. One gap worth knowing: the email send step is not in the authoring catalog yet, so an agent cannot add one. Build that step in the Boom app. A journey that already has one still runs and still reads back normally.
  • Extracted data: define the typed fields a conversation should yield, then read them back per participant or in aggregate. See extraction.
  • WhatsApp templates: see your WhatsApp numbers, then list, read, and create message templates.
  • Your agent’s own tools: list the HTTP tools your agent can call mid-conversation, and create or update one — the same tools you author in Agent Studio’s Herramientas section. Reading the credentials and environments they reference works too, so a tool can be built end to end without leaving the chat. Secrets are never returned; a tool references one by name. Requires an organization admin login, and only for organizations with Agent Studio. See the agent.
Adding participants to an initiative (and launching one) sends real WhatsApp messages to real customers. Any connected AI tool can do it, so check what a tool is doing before you let it run on its own. People on your Do Not Contact list are always skipped.
Destructive and outreach actions (deleting records, launching or cancelling initiatives, adding or stopping participants) require your Boom login to be an organization admin. So does anything that reads or writes your agent’s own tools, reading included — a tool definition carries the internal hosts your agent calls. Every other read works for any member.

One uniform surface

How MCP tools map one-to-one onto REST endpoints.

Quickstart

Work with the same data over the REST API.

Authentication

API keys for scripts and server-to-server calls.

Connect your database

Sync people and objects straight from your database.

Rate limits & errors

Limits and the shared error shape.