Raygun Mcp Server

What is Raygun Mcp Server about?

Enables interaction with Raygun's Crash Reporting and Real User Monitoring APIs through a Model Context Protocol (MCP) server, exposing a rich set of operations for applications, errors, deployments, sessions, performance data, source maps, and team management.

How to use Raygun Mcp Server?

1. Install – No separate installation required; the server runs directly with npx.
2. Configure – Supply the required RAYGUN_PAT_TOKEN environment variable (your Raygun Personal Access Token). Optionally set SOURCEMAP_ALLOWED_DIRS to restrict source‑map file access.
3. Run – Launch the server using the MCP command configuration (e.g., via Claude Desktop or manually with npx -y @raygun.io/mcp-server-raygun).
4. Interact – Communicate over stdio using any MCP‑compatible client or the MCP Inspector for debugging.

Key features of Raygun Mcp Server

• Application Management: list, retrieve, and regenerate API keys.
• Error Management: list groups, fetch details, resolve, activate, ignore, or permanently ignore errors.
• Deployment Management: list, get, delete, update, and reprocess deployment commits.
• User & Session Management: list customers, sessions, and fetch session details.
• Performance Monitoring: list pages, obtain time‑series or histogram metrics for pages and errors.
• Source Map Operations: list, get, update, delete, upload, and bulk‑delete source maps with optional directory restrictions.
• Team Management: handle invitations – list, send, retrieve, and revoke.
• Debugging Support: built‑in npm script npm run inspector launches the MCP Inspector UI.

Use cases of Raygun Mcp Server

• Automated CI/CD pipelines: integrate deployment creation, update, and commit reprocessing directly into build scripts.
• Monitoring dashboards: pull real‑time error and performance metrics for custom dashboards or alerts.
• Security‑aware source‑map handling: restrict source‑map uploads to specific directories, ensuring sensitive paths are protected.
• Team onboarding automation: programmatically send and manage Raygun team invitations for new developers.
• Incident response tooling: resolve or ignore error groups automatically based on external criteria.

FAQ from the Raygun Mcp Server

• What authentication is required? Provide a Raygun Personal Access Token via the RAYGUN_PAT_TOKEN environment variable.

• Do I need to install the server globally? No. The recommended approach is to run it with npx -y @raygun.io/mcp-server-raygun, which fetches the package at runtime.

• Can I restrict source‑map operations? Yes. Set SOURCEMAP_ALLOWED_DIRS to a comma‑separated list of permitted directories.

• How do I debug communication issues? Use the provided MCP Inspector (npm run inspector) which offers a web UI for inspecting stdio traffic.

• Is the server compatible with non‑Claude clients? Absolutely. Any MCP‑compatible client can communicate over stdio with the server.

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:

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

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

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

{
  "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:

npm run inspector

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