Raygun: Crash Master & Real-Time Insights

Master crashes and real-time data seamlessly with Raygun—track, analyze, and resolve issues across apps and infrastructure effortlessly.

Visit Repository

✨ Research And Data

4.4(67 reviews)

100 saves

46 comments

97% of users reported increased productivity after just one week

About Raygun

What is Raygun: Crash Master & Real-Time Insights?

Raygun: Crash Master & Real-Time Insights is a robust platform engineered to streamline error tracking, application monitoring, and team collaboration through its MCP Server architecture. By leveraging Raygun's API V3 endpoints, this solution empowers developers to gain granular control over crash reporting, user sessions, and performance metrics—ensuring seamless integration with modern development workflows.

How to Use Raygun: Crash Master & Real-Time Insights?

Initialization requires configuring the RAYGUN_PAT_TOKEN environment variable, which authenticates access to your account’s resources. For Claude Desktop users, integrating the server involves specifying its path and parameters in the claude_desktop_config.json. Developers can then execute commands via npm scripts to build, watch, or debug the server. For instance, deploying the server on macOS involves updating the configuration file with the server’s built path and securing token credentials.

Raygun Features

Key Features of Raygun: Crash Master & Real-Time Insights?

Error Mastery: Resolve, activate, or permanently ignore error groups with precise status transitions.
Deployment Control: Track, modify, or purge deployments while reprocessing commit data for deeper analysis.
Performance Profiling: Access time-series and histogram metrics for page load speeds and error rates.
Source Map Management: Upload, update, or bulk-delete source maps to enhance debugging clarity.
Collaborative Workflows: Manage team invitations and permissions to ensure secure access delegation.

Use Cases of Raygun: Crash Master & Real-Time Insights?

Engineering teams leverage this tool to:

Identify recurring crashes in production environments using error group analytics.
Correlate deployment timelines with performance dips to trace regression sources.
Optimize user experience by pinpointing slow-loading pages through histogram insights.
Automate source map uploads during CI/CD pipelines for seamless stack trace resolution.
Onboard new developers swiftly via programmable invitation workflows.

Raygun FAQ

FAQ from Raygun: Crash Master & Real-Time Insights?

Q: Can I restrict source map operations to specific directories?
Yes, the SOURCEMAP_ALLOWED_DIRS variable enforces directory-level access controls, enhancing operational safety.

Q: How do I troubleshoot server communication issues?
Utilize the MCP Inspector tool to visualize stdio interactions and diagnose protocol-level errors.

Q: Is multi-environment support available?
The server’s modular configuration permits separate PAT tokens and directories per environment, enabling frictionless deployment across staging/production tiers.

Content

Raygun MCP Server

MCP Server for Raygun's API V3 endpoints for interacting with your Crash Reporting and Real User Monitoring applications. This server provides comprehensive access to Raygun's API features through the Model Context Protocol.

Features

Tools

Applications

list_applications - List all applications under your account
get_application - Get application details by identifier
get_application_by_api_key - Get application details by API key
regenerate_application_api_key - Generate a new API key for an application

Error Management

list_error_groups - List error groups for an application
get_error_group - Get detailed information about an error group
resolve_error_group - Set error group status to resolved
activate_error_group - Set error group status to active
ignore_error_group - Set error group status to ignored
permanently_ignore_error_group - Set error group status to permanently ignored

Deployment Management

list_deployments - List deployments for an application
get_deployment - Get deployment details by identifier
delete_deployment - Remove a deployment
update_deployment - Update deployment information
reprocess_deployment_commits - Reprocess deployment commit data

User & Session Management

list_customers - List customers for an application
list_sessions - List user sessions for an application
get_session - Get detailed session information

Performance Monitoring

list_pages - List monitored pages for an application
get_page_metrics_time_series - Get time-series performance metrics
get_page_metrics_histogram - Get histogram of performance metrics
get_error_metrics_time_series - Get time-series error metrics

Source Maps

list_source_maps - List source maps for an application
get_source_map - Get source map details
update_source_map - Update source map information
delete_source_map - Remove a source map
upload_source_map - Upload a new source map
delete_all_source_maps - Remove all source maps

Team Management

list_invitations - List pending team invitations
send_invitation - Send a new team invitation
get_invitation - Get invitation details
revoke_invitation - Revoke a pending invitation

Configuration

The server requires the following environment variables:

RAYGUN_PAT_TOKEN (required): Your Raygun PAT token
SOURCEMAP_ALLOWED_DIRS (optional): Comma-separated list of directories allowed for source map operations

Usage with Claude Desktop

Add to your claude_desktop_config.json:

json { "mcpServers": { "raygun": { "command": "npx", "args": ["-y", "@raygun.io/mcp-server-raygun"], "env": { "RAYGUN_PAT_TOKEN": "your-pat-token-here" } } } }

Development

Install dependencies: bash npm install

Build the server: bash npm run build

For development with auto-rebuild: bash npm run watch

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

json { "mcpServers": { "raygun": { "command": "/path/to/server-raygun/build/index.js", "env": { "RAYGUN_PAT_TOKEN": "your-pat-token-ken" } } } }

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

bash npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.