Let your AI assistant work inside Broadkite.
Broadkite runs an MCP server, so Claude, Cursor or any MCP client can search your contacts, read replies, build segments and draft campaigns, with only the access you approve. Your assistant drafts. You decide what gets sent.
$ claude mcp add --transport http broadkite https://api.broadkite.com/v1/mcpAdded HTTP MCP server broadkite with URL: https://api.broadkite.com/v1/mcp to local config> /mcpOpening your browser to sign in to Broadkite…✔ Authenticated. broadkite is connected with the scopes you approved.> Find this week's unread replies and draft an answer to each one.● broadkite · list_threads (unseen_only: true) ⎿ 4 threads, newest first● broadkite · get_thread ×4● broadkite · draft_reply ×4Four drafts are ready, one per thread. Read them over and send from Broadkite.Ask in plain words. It picks the tools.
The server exposes more than a hundred tools across contacts, segments, campaigns, the inbox, deals, forms, automations and webhooks. Each one runs as you, through the same checks as the dashboard, so an assistant never does more than you could.
- Tools that send mail are never exposed. Over MCP the assistant writes drafts and you send them.
- The consent screen lists every scope the client asks for, capped at what your role allows.
- You can disconnect a client at any time from connected apps in the dashboard.
list_threads (unseen_only: true)Reads
4 threads, newest first
get_thread ×4Reads
Sender, subject and text of each message
Four people wrote back. Two ask about pricing, one wants a call next week and one is out of office.
draft_reply ×4Reads
Four drafts, addressed and titled from their threads
The drafts come back to you. Nothing leaves your mailbox until you send it.
list_segment_fieldsReads
The fields a condition can use
preview_segment (match: all, 2 conditions)Reads
312 contacts match
create_segment (name: "Austin dentists")Changes data
Saved
A saved segment of 312 contacts that keeps up on its own as contacts change.
create_campaign_draft (name: "Austin dentists")Changes data
Draft created, not started
add_campaign_step ×3Changes data
An opener, then follow-ups on day 3 and day 7
set_campaign_segmentsChanges data
Linked to Austin dentists
The campaign waits as a draft. Starting it is your call, in Broadkite.
get_dashboard_analytics (from: Nov 3, to: Nov 9)Reads
Sends, replies and bounces for the week
get_campaign_stats ×3Reads
The same numbers, campaign by campaign
A short read-out: which campaign drew the most replies and where the bounces came from.
list_deals_by_contactReads
One open deal, in Sales
move_deal_stage (stage: Proposal)Changes data
Moved
add_contact_noteChanges data
Saved on Dana's contact
The new stage and the note show up for the whole team, live.
Connected in one command.
Add the server, approve access in your browser and start asking. There is no key to copy. For a script or a CI job, create a scoped API key and send it as a header instead.
- Add the server to your assistant
- Sign in to Broadkite and approve the scopes
- Ask your first question
claude mcp add --transport http broadkite https://api.broadkite.com/v1/mcp
# then, inside Claude Code
/mcp{
"mcpServers": {
"broadkite": { "type": "http", "url": "https://api.broadkite.com/v1/mcp" }
}
}{
"mcpServers": {
"broadkite": { "url": "https://api.broadkite.com/v1/mcp" }
}
}claude mcp add --transport http broadkite https://api.broadkite.com/v1/mcp \
--header "Authorization: Bearer core_..."It works the other way too.
Broady, the assistant built into Broadkite, can use tools from MCP servers you connect under Settings, Connections. A new server starts switched off so you can read its tools first, and Broady asks before every call to an outside tool.
Pick a search tool on one of your servers and it becomes the workspace's web search, used by the lead finder and by Broady.
Connect an MCP serverCompany wiki
https://wiki.acme.com/mcp
Search
https://search.acme.com/mcp
Billing
https://billing.acme.com/mcp · 9 tools to review
The REST API, for your own code.
Every capability has an endpoint under /v1, described in an OpenAPI 3.1 file. Keys carry only the scopes you give them, a write with an Idempotency-Key never runs twice, and every error comes with a stable code and a request id.
Webhooks are signed with HMAC-SHA256 and retried up to 8 times, from 30 seconds apart up to an hour.
There is no official SDK. Generate a typed client from the OpenAPI file in your language, or call the API over plain HTTPS.
Open the API referencecurl -X POST "https://api.broadkite.com/v1/contacts" \
-H "Authorization: Bearer $CORE_API_KEY" \
-H "Idempotency-Key: 7f3c9a2e-import-01" \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]",
"first_name": "Dana",
"company": "Acme",
"campaigns": ["4c1d7a90-2f3b-4e8a-9d61-0b5e7f2c3a18"]
}'[
{
"id": "2c3d4e5f-6071-4b2c-9d3e-4f5a6b7c8d9e",
"email": "[email protected]",
"first_name": "Dana",
"company": "Acme",
"subscribed": true,
"campaigns": [{ "id": "4c1d7a90-…", "name": "Q3 outbound" }]
}
]{
"error": "Bad Request",
"message": "The request body is missing or has invalid fields: \"email\" is required.",
"code": "bad_request",
"request_id": "4bbbd1b2-8f86-47dd-8a7f-9476501ad20e"
}The same API from a terminal.
The core command line tool signs in once through your browser, then works with campaigns, contacts, mailboxes and the inbox from a shell, a CI job or an agent. The installer checks the download against the published checksum and installs nothing if they differ.
curl -fsSL https://broadkite.com/cli.sh | sh
core auth login
core campaign list
core inbox list --unseen
core api "/campaigns?limit=10"Plugs into the tools your team already uses.
HubSpot, Salesforce, Pipedrive and Slack connect with one sign-in. The rest take an API key or a webhook URL. Credentials are sealed with envelope encryption before they reach the database, and an expired token asks you to reconnect instead of failing quietly.
Apollo, Clay and CleanMyList connect too, and other developers publish community apps.
Browse every integrationHubSpot
CRMCreates or updates the contact and logs the reply as a note, or runs the workspace's whole CRM on HubSpot.
- Connects with
- One-click sign-in
Salesforce
CRMTwo-way sync: activity on the timeline, Lead Status written back, opt-outs in both directions, and imports from list views and Campaigns.
- Connects with
- One-click sign-in, for production, sandbox or My Domain
Pipedrive
CRMUpserts a person when they reply or when you ask, or runs the workspace's whole CRM on Pipedrive.
- Connects with
- One-click sign-in
Close
CRMUpserts a lead when they reply or when you ask.
- Connects with
- Close API key
Slack
Notifications and assistantRoutes notifications to channels or DMs, lets the team work inbox replies in a channel, and answers questions to the assistant right in Slack.
- Connects with
- One-click sign-in
Discord
NotificationsPings a server channel on a reply, a bounce or a change in warmup health.
- Connects with
- A Discord webhook URL
Zapier
AutomationSends Broadkite events to your Zap, and from there to anything Zapier connects to.
- Connects with
- A Broadkite API key
Make
AutomationSends Broadkite events to your Make scenario.
- Connects with
- A Broadkite API key
n8n
AutomationSends Broadkite events to your n8n workflow.
- Connects with
- A Broadkite API key
Calendly
MeetingsTracks booked, rescheduled and canceled calls, credited to the campaign that earned them.
- Connects with
- An inbound URL Broadkite creates for you
Cal.com
MeetingsTracks booked, rescheduled and canceled calls, credited to the campaign that earned them.
- Connects with
- An inbound URL Broadkite creates for you
MillionVerifier
VerificationChecks every contact's address with your own pay-as-you-go credits instead of the built-in check.
- Connects with
- MillionVerifier API key
Webhooks
Your own endpointSends signed events for replies, bounces, meetings and more to your endpoint, retried up to 8 times with backoff.
- Connects with
- An HTTPS URL you own
When something happens, the next step runs on its own.
An automation starts from a trigger, checks your conditions and runs its actions in order: update a CRM, post to Slack, add a contact to a campaign, open a deal. AI steps can read a reply and choose the route. No AI step ever sends email.
Build an automation- WhenReply receivedA contact replies to a campaign email
- Ifai_intent is wants_pricingWhat inbox tagging read in the reply
- ThenCreate a dealIn Sales, at the Qualified stage
- ThenSend a Slack messageTo #sales, with the contact and the subject
- WhenContact createdAdded by hand, through the API, by a form or by an automation
- ThenAdd a labelnew-lead
- ThenAdd to campaignWelcome sequence
- WhenForm submittedA hosted form receives a submission
- ThenCreate or update contactFrom the form's fields
- ThenAdd to campaignDemo follow-up
- WhenMeeting bookedA Calendly or Cal.com meeting is booked
- ThenMove the deal stageTo Meeting booked, in Sales
- ThenSend a Slack messageTo #sales
- WhenEmail bouncedA campaign email bounces
- ThenAdd a labelbounced
- ThenSend a webhookTo your own app, so it stops using the address
- WhenUnsubscribedA contact unsubscribes
- ThenCreate or update Pipedrive personSo the CRM holds the latest record
- WhenWarmup health changedA mailbox's warmup health state changes
- ThenSend a Discord messageTo #deliverability
- WhenDeliverability complaintA spam complaint is recorded
- ThenSend a Slack messageTo #deliverability
- ThenCreate a taskAssigned to the workspace owner
- WhenInbound webhookAn outside system posts to this automation's own URL
- ThenCreate or update contactFrom the posted fields
- ThenAdd to campaignInbound leads
- WhenCampaign actionA campaign reaches a Run automation step
- ThenAI stepSums up the conversation so far for the rep
- ThenCreate a taskCall the contact this week
MCP, API or SDK: which one do you need?
Most people only need the MCP server. Developers who want Broadkite inside their own product use the API.
What is MCP?
The Model Context Protocol is an open standard that lets an AI assistant use tools from other software. Broadkite's MCP server gives assistants such as Claude and Cursor a set of Broadkite tools, so you can work on your outreach by asking in plain words.
Do I need the API if I use MCP?
No. MCP is how you work through an assistant. The REST API is for your own code: syncing contacts from your app, reacting to webhooks, or building on Broadkite.
Is there an SDK?
Not an official one. The API is described in an OpenAPI 3.1 file at docs.broadkite.com/openapi.json, so you can generate a typed client for your language, or call the API over plain HTTPS.
Can my assistant send emails or start a campaign?
It cannot send a message: tools that send mail are never exposed over MCP, and over MCP an assistant only writes drafts. Starting a campaign needs the send campaigns scope, which a client signed in through the browser never gets. Only an API key you create with that scope can start one.
Which assistants work with it?
Any client that speaks MCP over streamable HTTP. The docs walk through Claude Code, Claude Desktop and Cursor, with a browser sign-in or an API key.
Can I connect it to Zapier, Make or n8n?
Yes. Each of them receives Broadkite events through a Broadkite API key and passes them on to anything it connects to.