Bugsnag MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUGSNAG_API_KEY | Yes | Your Bugsnag API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_organizationsA | List available Bugsnag organizations |
| list_projectsA | List projects in an organization |
| list_errorsC | List errors in a project with filtering options |
| view_errorB | Get detailed information about a specific error |
| list_error_eventsA | List events (occurrences) for a specific error |
| view_latest_eventC | View the latest event for an error |
| view_eventA | View detailed information about a specific event |
| view_stacktraceC | Extract and format stacktrace information from an event |
| view_exception_chainB | View the full chain of exceptions for an event |
| search_issuesC | Search for issues using various criteria |
| view_tabsA | View all event data tabs including app, device, user, request, breadcrumbs, metadata, and stacktrace |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools are clearly distinct, but list_errors and search_issues overlap in purpose (both list/filter errors/issues). view_latest_event is a convenience that could be derived from view_event, and view_stacktrace/view_exception_chain/view_tabs are similar views of event details, though their specific purposes are clear.
All tools follow a consistent verb_noun pattern (list_*, view_*, search_*) with snake_case throughout. The names are predictable and match their actions.
11 tools is well within the ideal range for an error-monitoring server. Each tool covers a distinct aspect of browsing organizations, projects, errors, and events without being excessive.
The tool set covers the main read-only workflows for Bugsnag: listing organizations/projects/errors/events, viewing details, and inspecting stacktraces. Minor gaps include no direct 'get project' tool and no ability to list events across a project (only per error), but these are workable.