1. Home
  2. Product Guides
  3. Raygun MCP server

Raygun MCP server

The Raygun Model Context Protocol (MCP) server lets compatible AI assistants investigate and manage Raygun data using natural-language requests.

The hosted Streamable HTTP endpoint is:

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

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

The server supports Crash Reporting, Real User Monitoring (RUM), Application Performance Monitoring (APM), deployments, applications, customers, metrics, and team invitations.

You need:

  • A Raygun account with access to an active plan.
  • An MCP client that supports remote Streamable HTTP servers.

OAuth is recommended and does not require you to create a token manually. Personal Access Token (PAT) authentication remains supported for clients without OAuth support and for automation.

Add the Raygun endpoint to your MCP client without an Authorization header. The client should discover Raygun's OAuth configuration automatically.

You do not need to supply an OAuth client ID or client secret. Raygun supports the automatic client registration mechanisms used by current MCP clients.

The first time you connect, your client opens Raygun in your browser. Sign in, select the plan you want the connection to access, review the requested permissions, and select Authorize. Your client stores and refreshes its OAuth credentials.

The authorization only provides access to the selected plan and does not give you permissions that your Raygun account does not already have.

note: Each OAuth connection is associated with one Raygun plan. To work with a different plan, add or reconnect a Raygun MCP configuration and select that plan during authorization. 

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

This configuration is shared by the Codex CLI, Codex IDE extension, and ChatGPT desktop app on the same Codex host.

In the ChatGPT desktop app, open Settings > MCP servers, select Add server, choose Streamable HTTP, and enter the Raygun endpoint. Save and restart the app, then select Authenticate for Raygun.

note: ChatGPT on the web uses remote MCP tools through Plugins and does not read your local Codex MCP configuration. The instructions above are for Codex and the ChatGPT desktop app; a separately published Raygun Plugin would be installed from the Plugins catalog in ChatGPT on the web. 

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

Run /mcp in Claude Code and follow the browser authentication flow.

Add the following remote server to your MCP configuration:

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

Add the following remote server to your MCP configuration:

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

Other OAuth-capable MCP clients only need the endpoint URL. The exact configuration property names vary by client.

If your MCP client does not support OAuth, create a Personal Access Token and select the permissions required for the Raygun tools you want to use.

Configure the endpoint with the token in the Authorization header. The configuration format is different for each client.

Set the RAYGUN_PAT environment variable, then add the server:

codex mcp add raygun --url https://api.raygun.com/v3/mcp --bearer-token-env-var RAYGUN_PAT

claude mcp add --transport http raygun https://api.raygun.com/v3/mcp \
  --header "Authorization: Bearer YOUR_PAT_TOKEN"

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

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

Keep PATs secure and never commit them to source control. PATs can be managed from your Raygun user settings.

After connecting, 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 user@example.com and explain where their experience failed.”
  • “Compare p95 page performance over the last seven days and identify the largest regression.”

The Raygun MCP server provides tools for:

  • Applications — Find applications, inspect application details, and rotate ingestion API keys.
  • Crash Reporting — Search and investigate error groups and occurrences, update error statuses, and manage investigation comments.
  • APM — Search and investigate performance issues and traces, and identify slow methods, queries, and external calls.
  • Deployments — List, create, inspect, update, and delete deployment records.
  • Customers and sessions — Find affected customers and inspect their sessions, environments, errors, and page journeys.
  • Pages and metrics — Analyze page performance distributions, performance trends, and error trends.
  • Team invitations — Review, send, and revoke invitations.

The MCP client receives each tool's current input and output schema directly from the server. See the complete Raygun MCP tool reference for the current tool list and suggested workflows.

During OAuth authorization, Raygun shows the permissions requested by the client. The hosted MCP server currently uses existing API v3 scopes for applications, APM, customers, deployments, Crash Reporting errors, invitations, metrics, RUM pages, and RUM sessions.

With PAT authentication, assign the equivalent scopes when creating the token. A missing scope results in an HTTP 403 response when a tool attempts the protected operation.

  • 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.

Confirm that your client supports OAuth for remote Streamable HTTP MCP servers and that you did not configure a custom Authorization header. If the client does not support OAuth, use a PAT instead.

Reconnect or reauthenticate the MCP server. If you are using a PAT, confirm that the header uses Bearer YOUR_PAT_TOKEN and that the token is valid.

The authenticated user or token does not have the required permission. Reconnect with the required OAuth permissions, or create a PAT with the required scopes and confirm that the user has access to the selected plan and application.

For help with your Raygun account or authorization, contact Raygun support. For MCP server bugs or tool requests, use the Raygun MCP server repository.

On this page: