search_events translates a question like slow checkout requests this week into Sentry's own query syntax, which removes the main barrier to using Sentry from an agent. On the hosted service that translation is included; run it yourself over stdio and you are supplying the LLM provider that does it. Scoping the URL to a project is the other setting worth getting right — it trims the discovery tools and stops every call needing an organization slug.
Sentry's hosted MCP service, aimed at coding agents rather than at general Sentry administration. It is a remote server at https://mcp.sentry.dev/mcp that can be scoped to one organization or one project, with a stdio transport available for self-hosted Sentry.
- Events searched in plain language and translated into Sentry's query syntax — across errors, spans, logs and metrics datasets — search_events
- Issues searched the same way, without knowing the query language — search_issues
- Anything addressed by its Sentry URL fetched directly, so a link pasted into chat resolves — get_sentry_resource
- Traces opened in full when a single request needs following end to end — get_trace_details
- AI conversations as a first-class shape: one row per conversation rather than per span, then the whole transcript by id — search_ai_conversations, get_ai_conversation_details
- Organizations and projects discovered when the connection is not already scoped — find_organizations, find_projects
- A searchable catalog for the rarer operations, so they do not all sit in the tool list — search_sentry_tools, execute_sentry_tool
- Project management through that catalog, when the skill is granted: projects created and updated, and team access added or removed — create_project, update_project, add_team_to_project, remove_team_from_project
A Sentry account, authorized over OAuth on first connection — the hosted endpoint needs nothing else. Scoping the URL to an organization, or better a project, makes tools default to it and hides the discovery tools you no longer need; ?experimental=1 turns on forward-looking variants. A Claude Code plugin installs it as a subagent that gets delegated Sentry questions automatically. For self-hosted Sentry there is a stdio transport driven by a user auth token — but the natural-language search tools need an LLM provider configured (OpenAI, Azure OpenAI, Anthropic or OpenRouter), and without one those specific tools are unavailable while the rest work normally.
One command plus a key — npx @sentry/mcp-server@latest --access-token=sentry-user-token, then supply credentials