Back to MCP Directory

Bugsnag

Model Context Protocol moderate risk

Bugsnag

The Bugsnag MCP server allows LLM tools to interact with Bugsnag for error monitoring, analysis, and issue management using an API key for authentication.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwrite

Quickstart

Install

npx bugsnag-mcp-server test-api-key your-bugsnag-api-key

Config

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

Exposed MCP Tools (10)

safe

list_organizations

Lists available Bugsnag organizations.

Read-only operation, no side effects.

safe

list_projects

Lists projects in a specified organization.

Read-only operation, no side effects.

safe

list_errors

Lists errors in a project, with filtering options.

Read-only operation, no side effects.

safe

view_error

Gets detailed information about a specific error.

Read-only operation, no side effects.

safe

list_error_events

Lists events (occurrences) for a specific error.

Read-only operation, no side effects.

safe

view_latest_event

Views the latest event for an error.

Read-only operation, no side effects.

safe

view_event

Views detailed information about a specific event.

Read-only operation, no side effects.

safe

view_stacktrace

Extracts and formats stacktrace information from an event.

Read-only operation, no side effects.

safe

view_exception_chain

Views the full chain of exceptions for an event.

Read-only operation, no side effects.

safe

search_issues

Searches for issues using various criteria.

Read-only operation, no side effects.

Safety Assessment

The Bugsnag MCP server is relatively safe for read-only operations. However, the ability to modify issues and the lack of sandboxing introduce moderate risks. Securely store and manage the Bugsnag API key to prevent unauthorized access.

API key authentication provides some access control.
Primarily focused on error monitoring and analysis, reducing risk of unintended damage.
No direct code execution capabilities.
Clear tool descriptions help understand potential impacts.

API key compromise could lead to unauthorized access to error data and issue management.
Write operations available, including issue updates and comments.
No mention of rate limiting, potentially leading to abuse.
Lack of sandboxing increases risk if the server is compromised.

Bugsnag Review, Pricing & Alternatives (2026) | Flaex AI