Back to integrations

BugSnag integration for background agents

Enable hosted BugSnag MCP access for errors and performance data.

Integration details

Connection

  • Hosted MCP via BugSnag OAuth

Agent actions

BugSnag MCP

  • bugsnag_list_projects

    List BugSnag projects available to the connected account.

  • bugsnag_get_current_project

    Get the current BugSnag project used by default for tool calls.

  • bugsnag_list_project_event_filters

    List filter fields available before searching project errors.

  • bugsnag_list_project_errors

    List and search errors in a BugSnag project.

  • bugsnag_get_error

    Get full details for a BugSnag error, including latest event context.

  • bugsnag_update_error

    Update an error status, severity, snooze state, or linked issue.

  • bugsnag_get_event

    Get detailed information for a specific BugSnag event.

  • bugsnag_get_event_details_from_dashboard_url

    Resolve a BugSnag dashboard URL into event details.

  • bugsnag_get_events_on_an_error

    List events grouped into a specific BugSnag error.

  • bugsnag_list_releases

    List releases for a BugSnag project.

  • bugsnag_get_release

    Get release details, source control metadata, and stability metrics.

  • bugsnag_get_build

    Get build details and stability metrics.

  • bugsnag_list_trace_fields

    List trace fields available for performance filtering.

  • bugsnag_list_span_groups

    List performance span groups tracked by BugSnag.

  • bugsnag_get_span_group

    Get detailed performance metrics for a span group.

  • bugsnag_list_spans

    List spans that belong to a span group.

  • bugsnag_get_trace

    Get all spans within a specific trace.

  • bugsnag_get_network_endpoint_groupings

    Get network endpoint grouping rules for a project.

  • bugsnag_set_network_endpoint_groupings

    Set network endpoint grouping rules for a project.

Credential safety

Credential-less sandboxes

Mistle lets agents access connected services without placing provider credentials inside the sandbox. Approved outbound requests are routed through Mistle's credential proxy, where authentication happens outside the agent runtime.

Credentials stay encrypted in Mistle's control plane and are applied only when a request is authorized for the calling sandbox and organization.

Read the credential-less sandboxes article
Diagram showing sandbox traffic routed through an egress proxy before credential injection.