MCPSTACK

Field reports on MCP servers — dev & devops · est. 2026

SEED LISTING — drafted before hands-on verification. Re-test before this case file is considered final.

Sentry MCP Server (official)

Use it

Observability / debugging · last verified 2026-07-29

VendorSentry (official)
Repo / hostgetsentry/sentry-mcp · hosted remote at mcp.sentry.dev
PricingFree with Sentry account (paid Sentry plans for real usage)
AuthOAuth (remote) or user token
TransportHosted remote or local
setup5/5
reliability4/5
capability3/5
maintenance5/5
trust4/5

What it does

Lets an agent search Sentry issues, read stack traces and breadcrumbs, inspect releases, and pull project context — so “why is prod erroring” becomes a question your coding agent can answer with real telemetry instead of guesses.

The short verdict

The hosted-remote-with-OAuth model is the direction the whole ecosystem is heading: nothing to install, auth handled by the vendor, works from any MCP client. The debugging loop (agent reads the actual stack trace, then fixes the code) is genuinely useful. Limitation: it is read-heavy — triage and context, not incident management.

Use it if: you run Sentry and your agent fixes bugs.

Skip if: you don't use Sentry — this is strictly a companion tool.

Reviewed on MCPstack? Add the badge

Reviewed on MCPstack: Sentry MCP Server (official)
[![Reviewed on MCPstack](https://mcpstack.dev/badge.svg)](https://mcpstack.dev/listings/sentry-mcp)