Raygun MCP server

What the model can do

Raygun crash reporting: applications, error groups by status with when each first and last occurred, one group's recent occurrence times, error counts over time per application or error group, and deployments with versions and commits; when you ask, can resolve, reactivate, ignore or permanently ignore error groups, comment on them, record, edit or delete deployments, and invite people to or revoke invitations from the Raygun plan.

Reads

• raygun_list_applicationsRaygun applications the token can see: identifier (used by every other Raygun tool), name, and whether each sends crash, APM or real-user data.
• raygun_list_error_groupsError groups in a Raygun application: message, status (active, resolved, ignored, permanentlyIgnored), when first seen and last occurred…
• raygun_get_error_groupOne Raygun error group with the times of its latest occurrences (up to 50, newest first).
• raygun_error_countsHow many errors a Raygun application recorded over time, in buckets (granularity such as 1h or 1d), optionally only for some error groups.
• raygun_list_deploymentsDeployments recorded in a Raygun application, newest first: version, who deployed, comment, commit and source control, and when.

Acts, when you ask

These change something in Raygun. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• raygun_resolve_error_groupMarks a Raygun error group resolved in the version you give; if it recurs in a later version it reactivates.
• raygun_activate_error_groupSets a resolved or ignored Raygun error group back to active.
• raygun_ignore_error_groupSets a Raygun error group to ignored; occurrences are still recorded.
• raygun_permanently_ignore_error_groupPermanently ignores a Raygun error group.
• raygun_comment_on_error_groupAdds a comment to a Raygun error group, visible to the team and sent to the application's integrations; the API cannot delete it.
• raygun_create_deploymentRecords a deployment of a version in a Raygun application, so errors can be tied to releases.
• raygun_update_deploymentEdits a Raygun deployment's version, owner, comment, commit or time; only the fields passed change.
• raygun_delete_deploymentPermanently deletes a deployment record from a Raygun application.
• raygun_invite_userEmails an invitation to join the token's Raygun plan to the address given; once accepted, that person gets access to the plan.
• raygun_revoke_invitationRevokes a pending Raygun invitation so it can no longer be accepted.

Connect it

First connect Raygun on Dashboard → Connections, then add Memtro to your client once. The Raygun tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Raygun connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which errors are new since yesterday's deployment?
• › How many errors did the API record per hour today?
• › When did the checkout timeout error first appear?
• › What was deployed to the web app last week?
• › Resolve the null reference error in version 2.3.

Questions

Is this an official Raygun MCP server?

No. It is Memtro's MCP server with Memtro's Raygun connector behind it: the connector reads Raygun through its API with the credentials you connect on Dashboard → Connections, and Raygun publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Raygun?

Only when you ask, and only what it has been granted: resolve an error group in a version; reactivate an error group; ignore an error group; permanently ignore an error group, optionally discarding new occurrences; comment on an error group; record a deployment; edit a deployment; delete a deployment; invite someone to the Raygun plan by email; revoke a pending invitation. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server