Labsco
MCP SERVER

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

Observability, Monitoring & Incident Response
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 and real user monitoring data. It is hosted at your Raygun API endpoint, so there is nothing to install — you authenticate with a personal access token and start asking.

What you get
  • Errors — `error_groups_list`, `error_group_investigate` for the full picture, `error_group_update_status` to resolve, ignore or reactivate, `error_group_add_comment` for investigation notes, `error_instances_browse` and `error_instance_get_details` for the stack trace and context of one occurrence
  • Deployments — `deployments_list`, `deployment_get_latest` with error analysis, `deployment_investigate`, `deployment_create` and `deployment_manage`
  • 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
  • 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 and a personal access token created at your Raygun user tokens page. The server is remote, at `https://api.raygun.com/v3/mcp`, so connecting is one command — `claude mcp add --transport http raygun https://api.raygun.com/v3/mcp --header "Authorization: Bearer YOUR_PAT_TOKEN"` — with equivalents documented for Amp, Cline, Codex, Cursor, Gemini CLI, JetBrains AI Assistant, VS Code and Zed. Keep the token out of version control; give it only the permissions your use actually needs.

Setup effort

One command plus a key — claude mcp add --transport http raygun https://api.raygun.com/v3/mcp --header "Authorization: Bearer YOUR_PAT_TOKEN", then supply credentials