Log inSubmit server
Bugsnag MCP logo

Bugsnag MCP

by tgeselle

Investigates Bugsnag organizations, projects, errors, events, stacktraces, and exception chains through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Bugsnag MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tgeselle-bugsnag-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bugsnag-mcp-server"
      ],
      "env": {
        "BUGSNAG_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y bugsnag-mcp-server

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

The tgeselle/bugsnag-mcp MCP server connects MCP-compatible AI clients to Bugsnag for error investigation. It exposes tools for navigating organizations and projects, filtering errors, inspecting events, searching issues, and reviewing formatted stacktraces with optional source context. Use it when an agent needs to trace a Bugsnag error from project discovery through event and exception analysis. It runs through npx and requires a Bugsnag API key.

Use cases

  • List Bugsnag organizations and projects
  • Filter open, fixed, or ignored errors
  • Inspect an error’s events and latest occurrence
  • Review stacktraces with source context
  • Search issues by error class or app version

Key features

  • Organization and project navigation
  • Status and sort filters for errors
  • Event history and detailed event views
  • Formatted stacktrace analysis
  • Exception chain inspection
  • Issue search by query, class, or app version

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

17/18 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · bugsnag-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars25Stargazers on the source repository.
npm downloads1.8kPackage downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

How Bugsnag MCP works

What tgeselle/bugsnag-mcp MCP server does

The tgeselle/bugsnag-mcp MCP server gives an MCP client a structured way to inspect data in Bugsnag. It covers organization and project discovery, error lists, individual error records, event history, event details, stacktraces, exception chains, and issue searches.

The server is intended for investigation workflows. An agent can identify an organization, find its projects, narrow a project’s errors by status or sort order, open a relevant error, and then inspect its latest or historical events. Searches can use a general query, error class, or app version. Stacktrace results can include nearby source code when that context is available.

How it works

The client starts the package as an MCP process and supplies BUGSNAG_API_KEY in its environment. The available tools then call Bugsnag using identifiers such as organization IDs, project IDs, error IDs, and event IDs. Most operations require the relevant ID, so the normal workflow begins with list_organizations and list_projects before moving into error or event inspection.

Error analysis is split across several tools. list_errors supports status filters for open, fixed, or ignored errors, along with newest, oldest, or priority sorting and a result limit. list_error_events returns occurrences for a selected error, while view_latest_event and view_event provide event-level inspection. view_stacktrace formats stack information and accepts an include_code option, which defaults to true. view_exception_chain exposes the full exception sequence for an event.

Setup and configuration

For the tgeselle/bugsnag-mcp MCP server, configure an MCP client to run npx -y bugsnag-mcp-server and set BUGSNAG_API_KEY to a Bugsnag access token. The README provides configurations for both Cursor and Claude Desktop using the same stdio command and environment variable.

The token is created in Bugsnag under Settings, Organization settings, and Access tokens. The documented permissions are read projects, read and write errors, and read and write comments.

The package can also be installed globally with npm install -g bugsnag-mcp-server, although the documented setup recommends running it with npx. To check a token independently, run npx bugsnag-mcp-server test-api-key your-bugsnag-api-key; a valid key displays Bugsnag projects and their IDs.

Tools and capabilities

The tgeselle/bugsnag-mcp MCP server exposes these tool groups:

  • Organization navigation: list_organizations and list_projects.
  • Error inspection: list_errors and view_error.
  • Event inspection: list_error_events, view_latest_event, and view_event.
  • Stack analysis: view_stacktrace and view_exception_chain.
  • Issue search: search_issues, with query, error-class, and app-version filters.

Together, these tools support locating recurring errors, comparing occurrences, reviewing event details, and following an exception chain toward a root cause.

Limitations and notes

A Bugsnag API key is required, and tool calls depend on valid organization, project, error, and event identifiers. Source snippets are only available when Bugsnag provides source code context. The documented configuration names Cursor and Claude Desktop; it does not describe additional client-specific setup.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Bugsnag MCP

tgeselle/bugsnag-mcp is an MCP server that connects AI clients to Bugsnag for investigating application errors. Its main tools list organizations, projects, errors, and events; show error and event details; search issues; format stacktraces with optional source context; and display exception chains.

Run it with npx using `npx -y bugsnag-mcp-server` in your MCP client configuration. Set the `BUGSNAG_API_KEY` environment variable to a Bugsnag access token. Global installation is also available with `npm install -g bugsnag-mcp-server`.

Yes, tgeselle/bugsnag-mcp works with Cursor using the documented npx MCP configuration. Add a server entry that runs `npx -y bugsnag-mcp-server` and provide your Bugsnag token through `BUGSNAG_API_KEY`.

Set `BUGSNAG_API_KEY` to a Bugsnag access token in the MCP server’s environment configuration. The README recommends permissions to read projects and read and write errors and comments, with tokens created under Bugsnag organization access-token settings.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBugsnag MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tgeselle-bugsnag-mcp?style=directory)](https://allmcps.com/mcp/tgeselle-bugsnag-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tgeselle-bugsnag-mcp"><img src="https://allmcps.com/api/badge/tgeselle-bugsnag-mcp?style=directory" alt="Bugsnag MCP on AllMCPs" /></a>