Breaker ships with an MCP server and a full API. Your model drafts campaigns, builds segments, and pulls the numbers. You review the work and press send.
MCP is an open standard that lets a model use outside tools. Breaker's MCP server hands your model the controls: campaigns, segments, contacts, and reports. Ask in plain English. Get answers from your live account data.
The fastest route for coding tools. Paste this into Claude Code, Codex, Cursor, or any AI coding assistant. It asks for your key, works out which client it is running in, registers the server, and checks the connection.
Set up the Breaker MCP server for me.
Breaker is an email newsletter platform. For this setup the MCP server runs
locally over stdio via npx and authenticates with an API key — do not look for
a browser sign-in or a hosted endpoint.
1. Ask me for my Breaker API key before you write any config. It looks like
bk_live_... . If I don't have one, tell me to create it at
https://app.breaker.email under Settings then API Keys, and wait for me. You
cannot create a key yourself.
2. Work out which MCP client you are running in and register the server using
that client's own method, named "breaker", at user scope where the client
has one.
Claude Code:
claude mcp add breaker --scope user \
--env BREAKER_API_KEY=bk_live_my_key_here \
-- npx -y -p @breaker-email/mcp breaker-mcp
Codex:
codex mcp add breaker --env BREAKER_API_KEY=bk_live_my_key_here \
-- npx -y -p @breaker-email/mcp breaker-mcp
Any other client — add this to its MCP config file:
{
"mcpServers": {
"breaker": {
"command": "npx",
"args": ["-y", "-p", "@breaker-email/mcp", "breaker-mcp"],
"env": { "BREAKER_API_KEY": "bk_live_my_key_here" }
}
}
}
Keep the -p flag and the breaker-mcp binary name exactly as written: npx is
told the package and the executable separately so it never has to guess.
VS Code uses the same shape under a "servers" key rather than "mcpServers".
BREAKER_API_KEY is required. Put the key in the env block — for a stdio
server this is the correct mechanism, not a workaround.
3. Confirm it worked before calling it done. Check the breaker tools are listed,
then call newsletter_get, which takes no arguments and only reads. Tell me
which newsletter it returned. A 401 means the key is wrong or revoked — tell
me, don't retry. During setup, never call a tool that creates, updates or
deletes anything.
4. A Breaker API key belongs to one newsletter. Once you know the name, offer to
rename the server to breaker-<newsletter> — lowercase, spaces and punctuation
replaced with dashes, so "Founders' Brief (EU)" becomes
breaker-founders-brief-eu. Useful if I run more than one newsletter. Only
rename if I say yes, and do it by removing and re-adding the server with the
same key.Nothing to install and no API key. Add Breaker's hosted endpoint as a custom connector and sign in with your Breaker account.
https://api.breaker.email/mcp
The connection is listed, and can be removed, in Breaker under Settings, Integrations, AI Clients. Run more than one newsletter? Add the connector once per newsletter and sign in to each.
One command, at user scope so every project sees it. Needs an API key from Settings, API Keys in the Breaker app.
claude mcp add breaker --scope user --env BREAKER_API_KEY=bk_live_your_key_here -- npx -y -p @breaker-email/mcp breaker-mcp
{
"mcpServers": {
"breaker": {
"command": "npx",
"args": ["-y", "-p", "@breaker-email/mcp", "breaker-mcp"],
"env": { "BREAKER_API_KEY": "bk_live_your_key_here" }
}
}
}Same as claude.ai: open Settings, Connectors, Add custom connector, paste the hosted URL, and sign in with your Breaker account. To run the server locally instead, open Settings, Developer, Edit Config, add this, and restart.
{
"mcpServers": {
"breaker": {
"command": "npx",
"args": ["-y", "-p", "@breaker-email/mcp", "breaker-mcp"],
"env": { "BREAKER_API_KEY": "bk_live_your_key_here" }
}
}
}ChatGPT connects to the hosted endpoint as an MCP app, added through Developer mode. No API key: you sign in with your Breaker account.
https://api.breaker.email/mcp
Developer mode is a beta feature on Plus and Pro plans. On Business, Enterprise and Edu workspaces an admin has to enable it first. The connection is listed, and can be removed, in Breaker under Settings, Integrations, AI Clients.
One command. Needs an API key from Settings, API Keys in the Breaker app. Codex stores its config as TOML, so the manual version looks different.
codex mcp add breaker --env BREAKER_API_KEY=bk_live_your_key_here -- npx -y -p @breaker-email/mcp breaker-mcp
[mcp_servers.breaker] command = "npx" args = ["-y", "-p", "@breaker-email/mcp", "breaker-mcp"] [mcp_servers.breaker.env] BREAKER_API_KEY = "bk_live_your_key_here"
Web clients that connect to a URL use the hosted endpoint and sign in with a Breaker account. Cursor, VS Code, Windsurf and any other client that speaks MCP over stdio can run the server locally: point it at npx -y -p @breaker-email/mcp breaker-mcp with BREAKER_API_KEY in the environment. VS Code uses the same shape under a servers key rather than mcpServers.
https://api.breaker.email/mcp
{
"mcpServers": {
"breaker": {
"command": "npx",
"args": ["-y", "-p", "@breaker-email/mcp", "breaker-mcp"],
"env": { "BREAKER_API_KEY": "bk_live_your_key_here" }
}
}
}The same tools whether you use the hosted endpoint or run the server yourself. It is a thin client of the public REST API: it holds no data and adds no behaviour of its own. Anything the API refuses, it refuses too.
Migrate your list and templates in an afternoon.