Error investigation
Search issues and events and inspect traces or performance signals.
Documentation ↗MCP server / observability / source-linked
Sentry MCP is a hosted, human-in-the-loop debugging server optimized for coding agents. It connects to Sentry through OAuth and can search errors, inspect performance, triage issues, read documentation, and manage projects. Organization/project URL scoping hides irrelevant discovery tools and is recommended for safer context.
Identify the implementation and the job it supports.
Sentry MCP is a hosted, human-in-the-loop debugging server optimized for coding agents. It connects to Sentry through OAuth and can search errors, inspect performance, triage issues, read documentation, and manage projects. Organization/project URL scoping hides irrelevant discovery tools and is recommended for safer context.
The documented interface, authentication and installation path.
Use the scoped https://mcp.sentry.dev/mcp/{organization}/{project} endpoint in a supported client and complete OAuth. For self-hosted stdio, install the package and pass a token.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp/ORG/PROJECTConcrete capabilities with maintainer sources.
Search issues and events and inspect traces or performance signals.
Documentation ↗Read or manage project information through the remote service.
Documentation ↗The official repository includes a Sentry-specific Claude subagent plugin for error and trace questions.
Documentation ↗What was checked and what was not tested.
Public maintainer documentation and repositories. This is not a hands-on product review.
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
A bounded evaluation you can reproduce in your own environment.
Suggested evaluation, not an observed test result.
What to inspect: A scoped incident brief linking symptoms, release context, and candidate next actions. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Read these constraints before granting access.
AI-powered search tools in stdio require an LLM provider; they are unavailable without one.
Boundary reference ↗Self-hosted stdio is described as work in progress and needs explicit token scopes; do not equate it with the hosted OAuth service.
Boundary reference ↗Make the expected output explicit before you connect.
A scoped incident brief linking symptoms, release context, and candidate next actions. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Grafana MCP | Choose when dashboards, logs, traces, and datasource queries span an observability stack. | Grafana requires managing instance credentials and server deployment for local use. Documentation ↗ |
| Vercel MCP | Choose when the failure is tied specifically to Vercel deployments and runtime logs. | Vercel scope is platform-specific; Sentry offers broader error context. Documentation ↗ |
Answers specific to this implementation.
No. Sentry says the service prioritizes human-in-the-loop developer debugging workflows.
Documentation ↗
Yes. Include organization and project slugs in the endpoint; scoped connections hide unnecessary discovery tools.
Documentation ↗
Maintainer documentation used in this record.