Sentry

Sentry ships the official integration as @sentry/mcp-server, maintained in getsentry/sentry-mcp. There was never an @modelcontextprotocol/server-sentry package on npm — use this one. Designed for stdio use inside Cursor, Claude Desktop, Claude Code, and VS Code. What it does: - Lists issues with environment, release, status, and assignee filters - Returns event detail including stack frames, breadcrumbs, and tags - Resolves, ignores, or reassigns issues to a teammate or team - Reads release and deploy metadata for a project - Enumerates projects, teams, and organisations the token has access to - Works against sentry.io as well as a self-hosted Sentry install Example: An on-call agent: "Show me issues from prod in the last 30 minutes that spiked above baseline, include the top stack frame for each, and group by release." One MCP conversation replaces three browser tabs of Sentry triage. Setup: SENTRY_AUTH_TOKEN for authentication and SENTRY_ORG for the org slug. For self-hosted Sentry set SENTRY_URL to the install's base URL. The token only needs event:read, project:read, and org:read for the read-only workflow; grant event:admin to enable resolve / ignore writes. Transport: stdio. Bundled as a single Node binary so "npx -y @sentry/mcp-server" is the full install story. Notes: The tool surface tracks Sentry's public API rather than drifting. If your install predates release-health support the release tools will return an explicit "not supported on this install" error instead of silently returning empty responses. For large orgs the issue list tool paginates — set a tighter environment filter if you are burning context on issues outside your scope.