[ MCP SERVER SUMMARY ]
Raygun MCP server summary
Interact with your crash reporting and real using monitoring data on your Raygun account Connect Raygun through Bifrost MCP Gateway to centralize access control, virtual keys, and tool-call observability for your AI assistants.
| Property | Details |
|---|---|
| Company | Upstream maintainer |
| Connection type | Confirm upstream transport |
| Authentication | Varies by upstream server |
| Package or endpoint | See upstream documentation |
| Capabilities | Raygun tools over MCP, AI assistant connectivity, Governed tool access through Bifrost |
| Official documentation | Raygun MCP documentation |
Before you start
- Review the Raygun upstream documentation for its installation requirements
- Obtain any credentials required by the upstream service
- A running Bifrost MCP Gateway instance
What you can do with Raygun
- Interact with your crash reporting and real using monitoring data on your Raygun account
- Expose Raygun tools to Claude, Cursor, and other MCP clients through one endpoint
- Apply virtual keys, tool allowlists, and audit logging at the gateway
[ HOW TO CONNECT ]
Connect Raygun to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Raygun in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and select the transport documented by the upstream server. Or register via the API below.
• Confirm the transport, command or endpoint, and authentication requirements in the Raygun upstream documentation.
• Replace every placeholder in the example before sending the request.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Raygun.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Raygun via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
# For a remote HTTP or SSE server:
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "raygun",
"connection_type": "<http|sse>",
"connection_string": "<upstream MCP endpoint>",
"tools_to_execute": ["*"]
}'
# For a local STDIO server:
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "raygun",
"connection_type": "stdio",
"stdio_config": {
"command": "<upstream command>",
"args": ["<arg>"]
},
"tools_to_execute": ["*"]
}'[ WHY BIFROST ]
Run Raygun through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Raygun MCP server do?
Interact with your crash reporting and real using monitoring data on your Raygun account The exact tools available depend on the upstream server version and configuration.
How do I connect Raygun to Bifrost?
Check the upstream documentation to determine whether Raygun uses STDIO, Streamable HTTP, or SSE. Then add it as an MCP client in Bifrost using the corresponding command or endpoint.
Does Bifrost replace the Raygun MCP server?
No. Bifrost connects to Raygun as an upstream MCP client and adds a governed gateway between that server and your AI assistants.
[ RELATED SERVERS ]
More MCP integrations
Quickchat AI
Launch your conversational Quickchat AI agent as an MCP to give AI apps real-time access to its Knowledge Base and conversational capabilities
Ragie
Retrieve context from your Ragie (RAG) knowledge base connected to integrations like Google Drive, Notion, JIRA and more.
Ramp
Interact with Ramp's Developer API to run analysis on your spend and gain insights leveraging LLMs