Raygun

✨ Key Features

• 🐛 Error Management - Investigate, resolve, and track application errors and crashes with full stack traces and context
• 🚀 Deployment Tracking - Monitor releases and correlate errors with deployments to identify problematic changes
• ⚡ Performance Insights - Analyze page load times, user metrics, and performance trends over time
• 🔬 APM Investigation - Find backend hotspots, recurring performance issues, and slow traces
• 👥 User Monitoring - Track customer sessions, behavior patterns, and identify affected users
• 🤝 Team Collaboration - Manage invitations and coordinate error resolution across your team
• 📊 Metrics & Analytics - Time-series analysis and distribution histograms for errors and performance

📋 Requirements

• A Raygun account with an active subscription
• An MCP client with OAuth support, or a Raygun Personal Access Token

🚀 Getting Started

The Raygun MCP server is hosted at:

https://api.raygun.com/v3/mcp

Raygun hosts and updates the service, so there is no package or local server to install.

[Install in Cursor] [Install in VS Code]

OAuth (recommended)

Add the URL as a Streamable HTTP server without an Authorization header. On first connection, your MCP client will open Raygun in your browser so you can sign in, select a plan, review the requested permissions, and authorize access.

You do not need to supply an OAuth client ID or client secret. Raygun supports automatic client registration.

codex mcp add raygun --url https://api.raygun.com/v3/mcpcodex mcp login raygun

claude mcp add --transport http raygun https://api.raygun.com/v3/mcp

{  "mcpServers": {    "raygun": {      "url": "https://api.raygun.com/v3/mcp"    }  }}

{  "servers": {    "raygun": {      "type": "http",      "url": "https://api.raygun.com/v3/mcp"    }  }}

Personal Access Token

PAT authentication remains supported for clients without MCP OAuth support and for automation. The following example uses Cursor's configuration format; other clients use the same Authorization header in their HTTP server configuration:

{  "mcpServers": {    "raygun": {      "url": "https://api.raygun.com/v3/mcp",      "headers": {        "Authorization": "Bearer YOUR_PAT_TOKEN"      }    }  }}

💬 Your First Prompt

After configuration, try asking your AI assistant:

• “Find the errors that first appeared after the latest deployment of my checkout application.”
• “Investigate the most frequently occurring production error and show me a representative stack trace.”
• “Which backend methods or database queries consumed the most time in the last 24 hours?”
• “Show me the last session for customer [email protected] and explain where their experience failed.”
• “Compare p95 page performance over the last seven days and identify the largest regression.”

🛠️ Tools

The Raygun MCP server provides the following categories of tools:

For detailed documentation on each tool, see the Tool Reference.

🔐 Authentication

OAuth

Raygun implements the MCP authorization flow for HTTP clients. The server advertises its authorization server through OAuth Protected Resource Metadata, and compatible clients register themselves automatically using Client ID Metadata Documents or Dynamic Client Registration.

Access is tied to the Raygun user, plan, and scopes approved on the consent screen. Compatible clients securely store and refresh their own tokens.

Each OAuth connection grants access to one Raygun plan. Add another Raygun MCP configuration and authorize it separately when you need to work with a different plan.

Security and access

• OAuth never gives the client more access than the signed-in Raygun user already has.
• Read and write access is controlled by the scopes approved during OAuth or assigned to the PAT.
• Some tools can change Raygun data, including error statuses, deployments, invitations, comments, and ingestion API keys. Review write actions before approving them in your MCP client.
• Application tools can return or rotate ingestion API keys. Treat returned keys as credentials; rotating a key immediately invalidates the previous one.
• Tool results may be included in conversations processed by your chosen AI client or model provider. Follow your organization's policies for sharing diagnostic and customer data.

Obtaining a Personal Access Token

PATs remain available when OAuth is not suitable:

1. Navigate to Raygun Personal Access Tokens
2. Click Create New Token
3. Give your token a descriptive name (e.g., "MCP Server Access")
4. Select the appropriate permissions for your use case
5. Copy the generated token and send it as Authorization: Bearer YOUR_PAT_TOKEN

Keep PATs secure and never commit them to version control.

For more details, see the Raygun API documentation.

📖 About

The Raygun MCP server enables AI assistants to investigate Crash Reporting, RUM, and APM data; track deployments; analyze performance; and manage application monitoring through natural-language conversations.

🔗 Resources

• 📚 Raygun Documentation
• 📘 Raygun MCP Setup Guide
• 🔌 Raygun API Reference
• 🤖 Model Context Protocol
• 🐛 Report Issues