Raygun MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Raygun MCP Server?

Raygun MCP Server is a server designed to interact with Raygun's API V3 endpoints, providing comprehensive access to crash reporting and real user monitoring applications through the Model Context Protocol.

how to use Raygun MCP Server?

To use the Raygun MCP Server, configure it with your Raygun PAT token and set it up in your Claude Desktop configuration. You can then run commands to manage applications, errors, deployments, and performance monitoring.

key features of Raygun MCP Server?

  • Manage applications and their API keys
  • Handle error management with detailed error group information
  • Monitor deployments and user sessions
  • Access performance metrics and source maps
  • Team management capabilities for collaboration

use cases of Raygun MCP Server?

  1. Integrating crash reporting into applications
  2. Monitoring real user performance metrics
  3. Managing application deployments and error resolutions

FAQ from Raygun MCP Server?

  • What is required to run the Raygun MCP Server?

You need to set the RAYGUN_PAT_TOKEN environment variable with your Raygun PAT token.

  • Can I use this server for multiple applications?

Yes! You can manage multiple applications under your Raygun account using this server.

  • How do I debug the server?

Use the MCP Inspector for debugging, which provides tools accessible via a browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago