Server facts
bugsnag-mcp
Project
- Author
- tgeselle
- Repository
- github.com/tgeselle/bugsnag-mcp
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- api blueprint
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 25
- Last commit
- Data as of
Overview
Bugsnag investigations can move from an organization’s project list to individual error occurrences through bugsnag-mcp. Developers using Cursor or Claude can browse organizations, select projects, and narrow error lists by status, with sorting by age or priority. Issue searches support query text, error class, and application version. Separate tools retrieve an error’s details, enumerate its recorded events, inspect the latest occurrence, or open a particular event. This supports a workflow that starts with finding a relevant issue and continues into the evidence attached to its occurrences.
For deeper diagnosis, stacktrace output can include surrounding source code when available, distinguish application code from library code, and highlight the lines associated with an error. Exception-chain inspection exposes related exceptions for an event. The view_tabs tool brings together event sections covering the application, device, user, request, breadcrumbs, metadata, and stacktrace. Access uses a Bugsnag API key, and the documented setup covers Cursor and Claude Desktop. Together, these tools support examining both the failure location and the contextual data recorded alongside it.
bugsnag-mcp setup notes
- bugsnag-mcp records stdio only; confirm a network transport upstream before planning remote access.
- bugsnag-mcp has no recorded license; confirm reuse terms in its repository.