Airbrake MCP server
Airbrake in any MCP client, through Memtro: Airbrake does not publish this server. Memtro's Airbrake connector reads Airbrake through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Airbrake error monitoring: projects with open and resolved error counts, errors (groups) by project or across all projects with message, top frames, occurrences and when last seen, a single error's occurrences, and deploys. Can mute or unmute an error, or delete it permanently.
Reads
airbrake_list_projectsAirbrake projects with unresolved and resolved error counts, total notices, rejected notices, deploy count and last deploy.airbrake_get_projectOne Airbrake project by id with its error, notice and deploy counts.airbrake_list_errorsErrors (Airbrake groups) in one project: type, message, top backtrace frames, environment, occurrences, first and last seen, resolved.airbrake_list_recent_errorsErrors (Airbrake groups) across every project this user can see, in Airbrake's own order.airbrake_get_errorOne Airbrake error (group) by project and id: type, message, top frames, occurrences, first and last seen.airbrake_list_occurrencesOccurrences (Airbrake notices) of one error: when, message, top frames, environment, host, app version and the names…airbrake_list_deploysDeploys recorded in one Airbrake project: environment, who deployed (username), repository, revision and version.
Acts, when you ask
These change something in Airbrake. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
airbrake_mute_errorMutes one Airbrake error (group): it leaves the project's default error list and stops sending notifications to everyone on the project until unmuted.airbrake_unmute_errorUnmutes one Airbrake error (group): it returns to the default list and notifies the project's team again when it recurs.airbrake_delete_errorPermanently deletes one Airbrake error (group) and all its recorded occurrences from the project, for everyone.
Connect it
First connect Airbrake on Dashboard → Connections, then add Memtro to your client once. The Airbrake tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Airbrake connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which app has the most open errors?
- › What is the noisiest error in the checkout project this week?
- › Did the errors start after yesterday's deploy?
- › Which hosts and app versions does the TimeoutError come from?
- › Mute the known Redis timeout error in the billing worker
Questions
- Is this an official Airbrake MCP server?
- No. It is Memtro's MCP server with Memtro's Airbrake connector behind it: the connector reads Airbrake through its API with the credentials you connect on Dashboard → Connections, and Airbrake publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Airbrake?
- Only when you ask, and only what it has been granted: mute an error so it leaves the default list and stops notifying the project, or unmute it again; delete an error and all its occurrences permanently. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.