Airbrake MCP Server

MCP (Model Context Protocol) server for Airbrake error tracking integration with Claude Code.

• List Airbrake projects
• List and filter error groups
• Get detailed error information with backtraces
• List individual error occurrences (notices)
• Resolve/unresolve errors
• Mute/unmute error notifications

• Ruby 3.0+
• Airbrake User API Key

gem install airbrake_mcp

git clone https://github.com/httplab/airbrake_mcp.git
cd airbrake_mcp
bundle install

1. Log in to Airbrake
2. Go to Profile Settings
3. Find "User API Key" section
4. Copy your key

claude mcp add airbrake airbrake_mcp \
  -e AIRBRAKE_USER_KEY=your_user_key \
  -e AIRBRAKE_PROJECT_ID=123456

If you use a Ruby version manager, Claude Code runs in a non-interactive shell without access to your shell profile. Provide the full path to the shim:

# rbenv
claude mcp add airbrake ~/.rbenv/shims/airbrake_mcp \
  -e AIRBRAKE_USER_KEY=your_user_key \
  -e AIRBRAKE_PROJECT_ID=123456

# asdf
claude mcp add airbrake ~/.asdf/shims/airbrake_mcp \
  -e AIRBRAKE_USER_KEY=your_user_key \
  -e AIRBRAKE_PROJECT_ID=123456

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "airbrake": {
      "command": "airbrake_mcp",
      "args": [],
      "env": {
        "AIRBRAKE_USER_KEY": "your_user_key",
        "AIRBRAKE_PROJECT_ID": "123456"
      }
    }
  }
}

List all Airbrake projects accessible to the user.

List error groups with filtering options.

Parameters:

• project_id (optional) - Project ID, uses default if not specified
• page (optional) - Page number, default: 1
• limit (optional) - Results per page, default: 20
• resolved (optional) - Filter by resolved status (true/false)

Get detailed information about a specific error group including backtrace.

Parameters:

• group_id (required) - Error group ID
• project_id (optional) - Project ID

List individual occurrences/notices for an error group.

Parameters:

• group_id (required) - Error group ID
• project_id (optional) - Project ID
• page (optional) - Page number, default: 1
• limit (optional) - Results per page, default: 10

Mark an error group as resolved or unresolve it.

Parameters:

• group_id (required) - Error group ID
• project_id (optional) - Project ID
• resolved (optional) - true to resolve, false to unresolve, default: true

Mute or unmute an error group (suppress/enable notifications).

Parameters:

• group_id (required) - Error group ID
• project_id (optional) - Project ID
• mute (optional) - true to mute, false to unmute, default: true

bundle exec rspec

# Build the gem
gem build airbrake_mcp.gemspec

# Install locally
gem install ./airbrake_mcp-*.gem --no-document

# If using rbenv, rehash to update shims
rbenv rehash

When updating the gem after code changes:

# 1. Remove ALL old versions
gem uninstall airbrake_mcp --all --executables --ignore-dependencies

# 2. Remove old gem files
rm -f *.gem

# 3. Build fresh gem
gem build airbrake_mcp.gemspec

# 4. Install with force flag
gem install ./airbrake_mcp-*.gem --no-document --force

# 5. Rehash rbenv shims
rbenv rehash

# 6. Verify installation
gem which airbrake_mcp

If you see rbenv: airbrake_mcp: command not found, the gem was installed for a different Ruby version.

# Check which Ruby versions have the gem
rbenv versions  # shows available versions
gem list airbrake_mcp  # shows if installed for current Ruby

# Install for the correct Ruby version
RBENV_VERSION=3.4.4 gem install ./airbrake_mcp-*.gem --no-document
rbenv rehash

1. Ensure the gem is completely uninstalled before reinstalling:

   gem uninstall airbrake_mcp --all --executables --ignore-dependencies

2. Verify the new code is in the built gem:

   gem unpack airbrake_mcp-*.gem --target=/tmp/check
   cat /tmp/check/airbrake_mcp-*/lib/airbrake_mcp/client.rb
   rm -rf /tmp/check

3. After installation, verify the installed code:

   cat $(dirname $(gem which airbrake_mcp))/airbrake_mcp/client.rb

Airbrake uses very large integers for error group IDs (e.g., 4235892606830408977). These IDs are passed as strings to avoid JavaScript precision loss issues. When using tools like get_error or list_notices, provide the group_id exactly as shown in list_errors output.

MIT