Airbrake MCP
Airbrake MCP Server is a MCP server that lets agents query Airbrake errors, notices, deploys, and project statistics.
About
Airbrake MCP Server lets developers and small teams surface Airbrake monitoring data inside Model Context Protocol agents. Instead of context-switching to the Airbrake dashboard during an incident, you can ask your coding agent to list errors, inspect notices, review recent deploys, and summarize project statistics—useful when you are iterating on fixes in the same IDE session. The package publishes as airbrake-mcp-server over stdio, matching standard Claude Code and Cursor MCP setups. It complements your existing Airbrake project configuration; it does not install SDKs or replace alert routing. Catalog placement is Operate under errors because the value peaks when production noise needs fast, agent-assisted investigation rather than during initial product ideation.
- Query Airbrake errors and notices from MCP clients
- Access deploy history tied to error spikes
- Pull project-level stats for triage context
- npm airbrake-mcp-server package at version 1.0.1
- stdio transport for local agent integration
Airbrake MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add airbrake-mcp-server -- npx -y airbrake-mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | airbrake-mcp-server |
|---|---|
| Transport | STDIO |
| Auth | None |
What it does
Investigate production Airbrake errors, notices, deploys, and project stats from Claude Code or Cursor without opening the Airbrake UI.
Who is it for?
Best when you already use Airbrake and want AI-assisted incident lookup from your MCP-enabled IDE.
Skip if: Greenfield projects with no Airbrake project or teams that rely solely on a different APM stack.
What you get
Your agent reads Airbrake through MCP so you can investigate notices, errors, deploys, and stats in one operational workflow.
- MCP-queryable Airbrake errors and notices
- Deploy and project statistics accessible from the agent
- Faster Operate-phase triage without leaving the IDE
By the numbers
- Server version 1.0.1
- npm identifier airbrake-mcp-server
- Documented capabilities: errors, notices, deploys, project stats
Recommended MCP Servers
Agent Audit MCPImmutable audit trail for agent-to-agent interactions2
Agentguard47 MCPRead-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.4
Agentic Observability MCPAgent tracing, cost tracking, anomaly detection for LLM agentsAgent Incident Relay MCPAgent Incident Relay MCP — Article 73 5-clock broadcaster.
Agent Infra MCP18 tools: agent memory, API drift detection, and HMAC-signed trust receipts
Agentmonitorrelay MCPAI agent run monitoring with incident replay and SLA receipts.How it compares
Airbrake observability MCP reader, not an error-fixing methodology skill.
FAQ
Who is io.github.Dach3r/airbrake-mcp-server for?
Developers running Airbrake in production who want Claude, Cursor, or similar agents to query errors, notices, deploys, and stats via MCP.
When should I use io.github.Dach3r/airbrake-mcp-server?
Use it in Operate during error triage, post-deploy checks, or when summarizing Airbrake project health from your agent session.
How do I add io.github.Dach3r/airbrake-mcp-server to my agent?
Install airbrake-mcp-server from npm, configure Airbrake credentials per the server repository docs, and register the stdio MCP entry in your client.