Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
The Sentry MCP server ends the stack-trace-paste ritual. Instead of copying error text into a chat window (losing breadcrumbs, tags, release context and frequency data in the process), your assistant queries Sentry directly: projects, issues, events with complete context — and can summon Seer, Sentry's own root-cause analysis agent, for the hard ones.
Debugging-by-URL is the signature move. Paste a Sentry issue link and ask "what's going on here?" — the assistant pulls the full event: exception chain, breadcrumbs leading in, affected release, user impact counts. With repo access alongside, the loop closes: error understood, offending code found, fix drafted, all in one thread. The difference between this and paste-the-traceback is the difference between reading a police report and visiting the scene.
Triage scales the same way: "what's new in production since yesterday's release?" or "which issues affect the most users this week?" become direct queries rather than dashboard sessions. For on-call, asking about a spike beats clicking through it.
The hosted server (mcp.sentry.dev, OAuth) is the recommended path and covers SaaS and self-hosted Sentry; a local stdio mode exists for the token-inclined. Access follows your Sentry permissions. The tool count is substantial (projects, issues, events, releases, DSNs, Seer invocation), but the daily gesture is simple: give it an error, get back understanding — which is, after all, what Sentry was always for.
update_issue resolves and assigns, which folds the bookkeeping half of triage into the same conversation instead of leaving a second pass in the UI for later.begin_seer_issue_fix starts it and the status tool collects the analysis. Kick it off at the start of a session and read the findings once you have the basics yourself.Paste a Sentry issue URL and get the full-context investigation.
"What broke since we shipped?" answered from real error data.
Seer analysis plus your repo-connected assistant closes error-to-fix.
| Tool | What it does |
|---|---|
| find_issues / get_issue_details | Query issues and read full event context |
| find_projects / find_releases | Project and release enumeration |
| get_event_attachment | Fetch event attachments |
| update_issue | Resolve, assign and manage issues |
| begin_seer_issue_fix / get_seer_issue_fix_status | Invoke Sentry's Seer root-cause agent |
| create_dsn / find_dsns | Manage project DSNs |
claude mcp add --transport http sentry https://mcp.sentry.dev/mcpA Sentry account (SaaS or self-hosted). OAuth for the hosted server; a user auth token for local mode.
| Variable | Description | Required |
|---|---|---|
| SENTRY_ACCESS_TOKEN | User auth token for local mode (remote uses OAuth) | Optional |
| SENTRY_HOST | Self-hosted Sentry hostname if applicable | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Query Onchain data, like ERC20 tokens, transaction history, smart contract state.
An MCP server for breaking down complex tasks into manageable pieces with structured JSON storage