MCP

Connect to remote Sentry MCP first, then look up debugging events

Fits people doing human-in-the-loop debugging in Cursor or Claude Code. Prefer the hosted service instead of jumping to stdio. search_events and search_issues also need an LLM provider configured; without it those two are unavailable, while the other tools still work.

Official source · sentry-mcp

Install

"url": "https://mcp.sentry.dev/mcp",
      "headers": {
        "Authorization": "Sentry-Bearer ${SENTRY_ACCESS_TOKEN}"
      }

Who it is for

If you need Sentry beside you while coding and accept human-in-the-loop rather than automating every Sentry feature, this service matches. Officially it is aimed mainly at human-in-the-loop coding agents; tool choice leans toward developer workflow and debugging, not a general full-feature Sentry MCP. It sits as a middle layer over the upstream Sentry API and is named as optimized for Cursor, Claude Code, and similar developer tools.

It is not suitable for people who want every Sentry feature, nor for people who do not yet have a Sentry access token but want to run stdio first. The current excerpt only clearly names AI search tools such as search_events and search_issues; other tools exist, but their names are not written in this excerpt. Do not invent missing tool names.

Read-only queries still go through the Sentry API; do not treat that as no network or no privacy boundary.

First try in 3 minutes

First prepare your own Sentry access token. The official recommended main path is the production hosted service, not installing stdio beside it:

The production notes entry is https://mcp.sentry.dev/ . The remote client config in the excerpt is:

"url": "https://mcp.sentry.dev/mcp ",
      "headers": {
        "Authorization": "Sentry-Bearer ${SENTRY_ACCESS_TOKEN}"
      }

Note that the auth scheme is Sentry-Bearer; do not change it to ordinary Bearer. Put this block in an MCP client that supports a remote URL, replace the token with your own value, and do not use any sample placeholder string. The excerpt does not hard-code a client file name.

After you connect, first raise a debugging question you already have in Sentry. If you have not configured an LLM provider (the excerpt lists OpenAI, Azure OpenAI, Anthropic, OpenRouter), do not call search_events or search_issues: without a provider those two are unavailable, while the remaining tools still work. The first try should prefer a still-available non-search tool for a read-only look; concrete names are not in the excerpt, so what can be confirmed stops at “tools other than AI search.”

The success signal is that the remote address https://mcp.sentry.dev/mcp can converse and return Sentry-side debugging information, not a 401, and not Authorization written as Bearer.

Use cases

Case 1: Do one debugging query in a coding assistant. The excerpt states this remote service targets developer workflow and debugging and sits as a middle layer over the Sentry API. Connect to the hosted URL first, then ask an existing debugging question. What can be confirmed is this middle-layer path; concrete non-search tool names and return fields do not appear in the current excerpt.

Case 2: Search events or issues in natural language. The excerpt states AI search tools such as search_events and search_issues need an LLM provider so they can turn natural language into Sentry query syntax. Confirm the provider is configured before you act. Without it these tools are unavailable; do not treat that failure as the whole service being down. Provider install commands and key variables are not in the excerpt; do not invent them.

These two cases correspond to “ordinary debugging tools” and “AI search.” Do not force the second path when the provider is not configured.

Limits

The main path is the hosted service https://mcp.sentry.dev/ and the remote MCP address https://mcp.sentry.dev/mcp . The excerpt also gives the stdio command npx @sentry/mcp-server@latest, and passes a User Auth Token you created yourself in Sentry with --access-token; do not fill in any sample placeholder. Scopes needed for stdio include org:read, project:read, project:write, team:read, team:write, event:write. Do not take this path the first time, and especially do not start with write scopes to perform writes.

The official repo is https://github.com/getsentry/sentry-mcp . It is not a full-feature Sentry API wrapper. Do not invent missing tool names, OAuth refresh behavior, or revoke steps.