![BugSnag](https://assets.smartbear.com/m/3945e02cdc983893/original/BugSnag-Repository-Header-Light.svg)

The BugSnag client provides comprehensive error monitoring and debugging capabilities as listed below. Tools for BugSnag require a `BUGSNAG_AUTH_TOKEN`.

If you wish to interact with only one BugSnag project, we also recommend setting `BUGSNAG_PROJECT_API_KEY` to reduce the scope of the conversation. This allows the MCP server to pre-cache your project's custom filters for better filtering prompts.

## Available Tools

### List Projects

-   Lists the projects in your organization.
-   Optionally locates a project by its API key.

### List Project Errors

-   Lists the open errors in the configured project with some basic details, taking an optional set of filters.
-   The project ID parameter is required if no project API key is configured.

### Get Error

-   Retrieves detailed information about the specified error.
-   In addition to the basic error details, it includes:
  -   Details of the latest event (occurrence) of the error – including stacktrace, user context and device information.
  -   Summaries (pivots) of the aggregated event data – for example app version, OS versions and any custom filters configured.
  -   Link to the error on the dashboard.
-   This tool also takes filter parameters in the same format as List Errors to specialize the results returned in the summaries/pivots.

### Get Events on an Error

-   Retrieves a list of events (occurrences) for a specified error, with complete details for each event.
-   This tool also takes filter parameters in the same format as List Errors to filter the events returned.

### Get Event Details

-   Retrieve event (occurrence) details of a specific event by ID.
-   This includes all the information about the event, including any thread traces which are trimmed in the Get Error tool.

### Get Event Details From Dashboard URL

-   Retrieve event (occurrence) details from a dashboard URL.
-   This is useful if you are copying the link from your dashboard to your IDE.

### List Project Event Filters

-   Lists the filters available for the current/specified project.
-   These filters can be used in the List Errors and Get Error tools to refine the results.

### Update Error

-   Allows you to update the status of the specified error to mark it as Open, Fixed, Ignored, Snoozed, Discarded or Undiscarded.
-   The severity can also be overridden from the default calculated value.
-   Link and unlink issues for a specified error.

### List Releases

-   List the releases for a given release stage (defaults to "production").
-   Optional filtering of hidden releases.
-   Each release contains the stability score and target information.

### Get Release

-   Get detailed information about a specific release, including source control information and metadata.
-   The tool also returns a summary of the builds that make up the release.

### Get Build

-   Get detailed information about a specific build, including source control information and metadata.

### Get Current Project

-   Retrieve details of the currently configured project.
-   This is either set via the `BUGSNAG_PROJECT_API_KEY` environment variable or from project IDs provided to other tools.

### List Span Groups

-   List span groups in your project.
-   Sort by various performance metrics including duration percentiles (p50, p75, p90, p95, p99), CPU usage, memory usage, frame rates, and HTTP error rates.
-   Filter to starred/important span groups or apply custom filters using trace fields.

### Get Span Group

-   Get detailed performance metrics for a specific span group.
-   Includes statistics across multiple percentiles (p50, p75, p90, p95, p99).
-   Shows timeline and distribution data for performance analysis.
-   Check registered performance targets for the operation.
-   Filter results using trace fields to narrow analysis to specific conditions.

### List Spans

-   Get individual span instances belonging to a specific span group.
-   Sort by duration, timestamp, page load metrics, frame rates, system metrics, or HTTP response codes.
-   Analyze individual slow operations to debug performance issues.
-   Each span includes a trace ID for further investigation.
-   Supports pagination and filtering by trace fields.

### Get Trace

-   Get all spans within a specific trace to view the complete execution path of a request/transaction.
-   View the hierarchy and timing of all operations in a distributed trace.
-   Identify bottlenecks by examining the complete flow through your system.
-   Supports pagination and can focus on a specific target span within the trace.

### List Trace Fields

-   Lists the custom attributes/fields available for filtering performance data.
-   These fields can be used in filters for List Span Groups, Get Span Group, List Spans, and Get Trace tools.

### Get Network Endpoint Groupings

-   Retrieve the current network endpoint grouping rules for a project.
-   Shows URL patterns used to consolidate similar network requests into single span groups.

### Set Network Endpoint Groupings

-   Configure URL patterns to control how network spans are grouped in performance monitoring.
-   Uses OpenAPI path templating syntax with curly braces for path parameters (e.g., `/users/{userId}`).
-   Supports wildcards (*) in domains to match multiple subdomains (e.g., `https://*.example.com`).
-   Converts colon-prefixed parameters from frameworks like Express/React Router (e.g., `:userId` → `{userId}`).

## Available Resources

### Event

Refers to an occurrence of an error: `bugsnag://event/{id}`.

## Configuration Notes

-   **Required Environment Variables**: `BUGSNAG_AUTH_TOKEN` is required for all operations.
-   **Optional Environment Variables**: `BUGSNAG_PROJECT_API_KEY` to scope operations to a single project and enable project-specific caching.
-   **Project Scoping**: When `BUGSNAG_PROJECT_API_KEY` is configured:
    -   The `list_bugsnag_projects` tool is not available (since you're already scoped to one project)
    -   The `projectId` parameter becomes optional for other tools
    -   Project event filters are pre-cached for better performance
-   **Filtering**: Use `get_project_event_filters` to discover available filter fields before using `list_bugsnag_project_errors`
-   **Time Filters**: Support both relative format (e.g., `7d`, `24h`) and ISO 8601 UTC format (e.g., `2018-05-20T00:00:00Z`)
-   **On-Premise Support**: Set the `BUGSNAG_ENDPOINT` environment variable to your custom endpoint if you're using an on-premise installation of BugSnag.
