bugsnag-mcp

Bugsnag MCP Server is a server that follows the Model Context Protocol (MCP) for interacting with Bugsnag, enabling LLM tools such as Cursor and Claude to investigate and resolve issues in Bugsnag.

Main Capabilities

• Error Monitoring and Analysis: Organization and project navigation for easy browsing of the Bugsnag hierarchy; error and event filtering with support for multiple filter options; detailed stack trace viewing showing formatted stack traces, source code context, and highlighted error lines; exception chain visualization to understand root causes by viewing the complete exception chain.
• Code Intelligence: Distinguish project code from library code, clearly identifying user code and third-party libraries; source code context to view relevant code snippets around the error location; error patterns to identify recurring patterns across multiple errors.
• Issue Management: Search capabilities to find issues by error class, message, or app version; error details to get comprehensive information for each error; event history to view all occurrences of a specific error.

Usage

Setting up the Bugsnag MCP Server is simple, with no need to install or download source code.

Add the Bugsnag MCP Server configuration:

{
  "mcpServers": {
    "bugsnag": {
      "command": "npx",
      "args": ["-y", "bugsnag-mcp-server"],
      "env": {
        "BUGSNAG_API_KEY": "your-bugsnag-api-key"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Replace your-bugsnag-api-key with your Bugsnag API key. For Claude Desktop, add this configuration as well.

Getting a Bugsnag API Key

1. Log in to your Bugsnag account:https://app.bugsnag.com/
2. Go to Settings > Organization settings > Access tokens
3. Create a new personal access token, which requires the following permissions: Read projects, Read and write errors, Read and write comments
4. Copy the generated token for the MCP server

Usage Examples

After configuration, you can use the Bugsnag MCP Server in LLM tools. Example prompts include: exploring Bugsnag accounts, finding and analyzing errors, and searching for specific issues.

Available Tools

• Organization and Project Management: List available Bugsnag organizations; list projects in an organization (requires organization_id).
• Error and Event Management: List errors in a project (requires project_id, optional status, sort, limit); get detailed information for a specific error (requires error_id); list events for a specific error (optional limit); view the latest event for an error; view detailed information for a specific event (requires event_id).
• Stack Trace Analysis: Extract and format stack trace information from an event (optional include_code, default true); view the complete exception chain of an event.
• Search: Search for issues using multiple conditions (optional query, error_class, app_version).

Advanced Usage

Testing the API Key

You can use a command to test whether the Bugsnag API key is valid. If valid, a list of Bugsnag projects and their IDs will be displayed.

Installation Options

npx is recommended, but you can also install the package globally. If you want to contribute or modify the code:

• Clone the repository:git clone https://github.com/yourusername/bugsnag-mcp.git then cd bugsnag-mcp
• Install dependencies:npm install
• Build the project:npm run build
• Run tests:npm test
• Run tests with coverage:npm run test:coverage
• Check code formatting: use Prettier

Continuous Integration

The project uses GitHub Actions for continuous integration. The workflow automatically: runs on pushes to the main branch and on pull requests; tests against multiple Node.js versions (18.x and 20.x); runs the test suite; generates and uploads test coverage reports; checks code formatting with Prettier. The workflow configuration is located at .github/workflows/test.yml and .github/workflows/prettier.yml.

Applicable Scenarios

Applicable when a development team uses Bugsnag for error monitoring, quickly investigates, analyzes, and resolves errors through LLM tools, improving debugging efficiency.

Limitations

The materials do not provide further information regarding fees, pricing, platform support, effectiveness, etc.