MCP serverValidated

Sentry MCP — debug from real errors, not guesses

Sentry's official server: pull real production errors, stack traces, and event context into the session — so a fix targets the actual failure and 'is it fixed' is checkable against the issue stream.

io.sentry/mcpOfficial docs →

A vetted listing, not an install — add the config to your MCP client yourself. CoSquared never writes MCP config.

Why this one

Calibration means checking claims against reality; production error data is the reality a backend fix has to answer to.

How to use it

  1. 1Start a bug fix from the Sentry issue, not the symptom report
  2. 2After deploying, check the issue actually stopped firing

Client config

Placeholders only — bring your own values

{
  "mcpServers": {
    "sentry": {
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}

Security notes

Error events often contain user data — request payloads, IPs, identifiers — and all of it enters model context when the agent reads an issue. Ensure your Sentry data-scrubbing rules are on before connecting, and scope OAuth to the projects you debug.