Skip to main content

Connector: Sentry

What it provides

Read error events, exceptions, and performance issues from Sentry.
The Debugger uses this to correlate production errors with commits and PRs.
The Auditor uses this to identify recurring security-relevant errors.

Available Tools

ToolDescriptionMembers
sentry.issues.listList recent unresolved issuesDebugger, Auditor
sentry.issues.getRead a specific issue with full stack traceDebugger
sentry.events.listList recent error eventsDebugger
sentry.releases.listList releases and their error ratesHerald, Debugger
sentry.releases.getGet error rate for a specific releaseHerald

Primary Members

  • The Debugger — reads error events to diagnose production issues
  • The Auditor — looks for security-relevant errors (auth failures, injection attempts)
  • The Herald — checks error rate after a release before announcing it as stable

Setup

{
  "mcp": {
    "servers": {
      "sentry": {
        "command": "npx",
        "args": ["-y", "@modelcontextprotocol/server-sentry"],
        "env": {
          "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
          "SENTRY_ORG": "${SENTRY_ORG}"
        }
      }
    }
  }
}

Notes

  • Requires a Sentry auth token with project:read scope
  • The Debugger correlates Sentry errors with git commits using the release tag
  • Tag your releases in Sentry with the same version as your git tags for best results