Raygun MCP Server

If you want an AI assistant working directly with Raygun, the raygun mcp server is the bridge. Interact with your crash reporting and real using monitoring data on your Raygun account.

What Raygun does

A remote Model Context Protocol (MCP) server that connects AI assistants to your crash reporting and real user monitoring data in Raygun through natural language conversations.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• applications_list — List all applications in your Raygun account
• applications_search — Search for applications by name
• application_get_details — Get detailed application information
• application_regenerate_api_key — Generate a new API key for an application
• error_groups_list — List error groups within an application
• error_group_investigate — Get complete details about a specific error group
• error_group_update_status — Change error group status (resolve, ignore, activate)
• error_group_add_comment — Add investigation notes to an error group
• error_instances_browse — Browse individual error occurrences
• error_instance_get_details — Get full stack trace and context for an error instance
• deployments_list — List deployments for an application
• deployment_create — Create a new deployment record
• deployment_get_latest — Get the most recent deployment with error analysis
• deployment_investigate — Get comprehensive deployment information

Installing the raygun mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: YOUR_PAT_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. Raygun sits in that group, and the shape of its toolset — applications_list, applications_search, application_get_details among others — tells you what it is really for. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Raygun.
• Written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the raygun mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.