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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago