airbrake-mcp-server

Airbrake MCP Server

Model Context Protocol (MCP) server for Airbrake. It lets you query errors, manage deploys, and fetch project stats directly from your MCP client.

Requirements

• Node.js 18+ (recommended 20+)
• Airbrake API key with read/write permissions
• Airbrake Project ID

Install

npm install
npm run build

VS Code MCP

This repo now includes the pieces needed to run as a VS Code MCP server and to publish to the MCP Registry:

• .vscode/mcp.json for direct workspace installation
• server.json for MCP Registry publication
• mcpName in package.json for npm ownership verification

Quick start in VS Code

• Open this folder in VS Code.
• Run MCP: Open Workspace Folder Configuration or MCP: List Servers.
• The committed .vscode/mcp.json points to npx -y airbrake-mcp-server.
• Enter your Airbrake API key and project ID when VS Code prompts for them.

Install from the MCP Gallery

Once the package is published to npm and registered in the MCP Registry, it can be installed from the VS Code MCP gallery by searching for @mcp airbrake.

Automated publishing

This repo includes a GitHub Actions workflow at .github/workflows/publish-mcp-registry.yml that publishes to the MCP Registry on version tags like v1.0.0 using GitHub OIDC.

Configuration

Set the following environment variables:

export AIRBRAKE_API_KEY="your_api_key"
export AIRBRAKE_PROJECT_ID="your_project_id"
export AIRBRAKE_HOST="https://api.airbrake.io"  # optional

Where to get credentials

• Open your project in Airbrake
• Go to Settings → API Keys
• Create a new API key with read/write permissions
• Your Project ID is in the project URL

Configure in Cursor

Edit your global MCP config:

/Users/<your-username>/.cursor/mcp.json

Example:

{
  "mcpServers": {
    "airbrake": {
      "command": "/absolute/path/to/node", // which node
      "args": ["/absolute/path/to/airbrake-mcp-server/dist/index.js"],
      "env": {
        "AIRBRAKE_API_KEY": "your_api_key",
        "AIRBRAKE_PROJECT_ID": "your_project_id"
      }
    }
  }
}

Notes

• Use absolute paths for command and args. Relative paths may fail because MCP is started from a different working directory.
• If you use a version manager (mise, nvm, asdf), point command to the actual Node binary shown by which node.
• If you want logs during startup, set AIRBRAKE_MCP_DEBUG=1 in env.
• If you use the workspace configuration in this repo, VS Code will prompt for the Airbrake credentials instead of requiring you to edit the file manually.

Tools (Available Commands)

Error Queries

• list_errors: List recent errors (pagination supported)
• get_error_details: Full details for a specific error group
• get_error_notices: All occurrences (notices) for an error group
• get_notice_details: Full details of a single notice

Search & Filter

• search_errors: Text search across errors
• filter_errors_by_status: Filter by open, resolved, or ignored
• get_error_trend: Occurrence trend over time

Error Management

• resolve_error: Mark error as resolved
• ignore_error: Mark error as ignored
• reopen_error: Reopen a resolved/ignored error

Deploys

• list_deploys: List recent deploys
• create_deploy: Create a deploy notification

Stats

• get_project_stats: Project health and statistics

Usage Examples

These depend on your MCP client, but typical prompts look like:

List the last 20 Airbrake errors
Get details for error 123456
Search errors for "NoMethodError"
Resolve error 123456

Development

npm run watch
npm run dev

Resources

• Airbrake API docs: https://airbrake.io/docs/api/
• MCP: https://modelcontextprotocol.io/