LabscoMCP early access ↗
MindscapeHQMCP SERVER · OFFICIAL PROJECT

Raygun

Investigate Raygun crash reports, real user monitoring and APM by asking — errors, deployments, performance and affected customers.

by MindscapeHQ ↗Observability, Monitoring & Incident Response✓ Official

LABSCO SUMMARY

From the crash to the release that caused it, in one thread.

The deployment tools are what make this more than an error viewer: an assistant can pull the newest release with its error analysis attached, then walk into the specific error group's stack trace — which is the actual shape of a post-release investigation.

What it is

A remote MCP server run by Raygun that connects an AI assistant to your Crash Reporting, Real User Monitoring and APM data. Raygun hosts it at https://api.raygun.com/v3/mcp, so there is no package or local server to install — you add the URL to your client and sign in.

What you get

  • Errors — error_groups_list, error_groups_search across messages, stack traces, URLs, versions, tags and affected users, error_group_investigate for the full picture, error_group_update_status to resolve, ignore or reactivate, error_group_add_comment and error_group_read_comments for investigation notes, error_group_instances_list and error_instance_get for the stack trace and context of one occurrence
  • Deployments — deployments_list, deployment_get_latest with its related error groups, deployment_investigate, deployment_create and deployment_manage
  • Backend performance (APM) — apm_hotspots_search to rank slow methods, database queries and external calls, apm_issues_search for recurring problems such as N+1 queries, apm_issue_investigate, apm_traces_search and apm_trace_investigate for one request's significant calls
  • Applications — applications_list, applications_search, application_get_details, application_regenerate_api_key
  • Customers and sessions — customers_search by name, email or identifier, customer_investigate for a profile with their recent errors and sessions, sessions_list with environment and device data, session_investigate for one session's errors and page journey
  • Page performance — pages_list, page_investigate, metrics_website_performance_analyze for trends, metrics_performance_distribution_analyze for variability, metrics_error_trends_analyze for error rates
  • Team — invitations_manage, invitation_send, invitation_revoke

Requirements

A Raygun account with an active subscription. Clients with MCP OAuth, including Claude Code, Codex, Cursor, VS Code and Zed, open Raygun in your browser to sign in, so there is no token to create; the others send a personal access token from app.raygun.com/user/tokens as an Authorization: Bearer header. Tools that change data (error statuses, deployments, comments, invitations, ingestion API keys) follow the scopes you approve, so grant only what you need.

Setup effort

One command, then sign in — claude mcp add --transport http raygun https://api.raygun.com/v3/mcp, then approve the OAuth sign-in