Sentry MCP Server

About

The Sentry MCP Server is Sentry's official Model Context Protocol integration, purpose-built for human-in-the-loop coding agents like Claude Code, Cursor, and Windsurf. Rather than exposing every Sentry API endpoint, it focuses tightly on developer debugging workflows: searching and triaging issues, pulling stack traces and event details, inspecting performance traces, and querying project/team/org metadata in natural language. The primary deployment is a hosted remote MCP server at mcp.sentry.dev, built on Cloudflare's remote-MCP infrastructure, so most users connect with zero local setup — just add the remote URL to their client. For self-hosted Sentry instances or local development, a stdio transport is also available via npx @sentry/mcp-server, authenticated with a Sentry User Auth Token scoped to org:read, project:read, project:write, team:read, team:write, and event:write. AI-powered search tools (search_events, search_issues) translate natural-language queries into Sentry's query syntax, but require a configured LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter) — all other tools work without one. Claude Code users can also install it as a plugin (claude plugin install sentry-mcp@sentry-mcp) for automatic subagent delegation whenever a conversation touches Sentry errors, issues, or traces. This turns "why did this deploy break in production" into a direct conversational debugging session instead of tab-switching into the Sentry dashboard.

Installation

npx @sentry/mcp-server@latest --access-token=YOUR_SENTRY_TOKEN

Connecting to Sentry MCP

1. 1.Sentry SaaS — use the remote server

   Point any OAuth-capable client at https://mcp.sentry.dev/mcp and complete the browser flow. There is no token to mint and nothing to install.

   shell

   claude mcp add --transport http sentry https://mcp.sentry.dev/mcp

2. 2.Claude Code, as a plugin instead

   Installing it as a plugin gives you a sentry-mcp subagent that Claude delegates to automatically whenever the conversation touches Sentry errors, issues, traces or performance — rather than you having to steer every lookup. A separate experimental marketplace channel carries forward-looking tool variants.

   shell

   claude plugin marketplace add getsentry/sentry-mcp
   claude plugin install sentry-mcp@sentry-mcp

3. 3.Remote, but with your own Sentry token

   Clients that support custom headers can pass an upstream Sentry API token to the Cloudflare transport using the Sentry-Bearer scheme. This is intentionally not Bearer — Bearer is reserved for MCP OAuth access tokens. With Sentry-Bearer the worker does not store, validate, exchange or refresh the token; it forwards it through the same API calls an OAuth session would use, and token lifetime stays your problem.

   json

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

4. 4.Narrow what a direct-auth session can reach

   Direct remote auth defaults to every active MCP skill. Append ?skills=inspect,triage to expose only those, or ?disable-skills=seer to drop one. Worth doing on any connection you are not supervising.

   url

   https://mcp.sentry.dev/mcp?skills=inspect,triage

5. 5.Self-hosted Sentry — stdio

   Create a User Auth Token with scopes org:read, project:read, project:write, team:read, team:write and event:write, then launch the stdio transport with --host set to the hostname only (no scheme, no path). Leave the host unset and the CLI targets Sentry SaaS.

   shell

   npx @sentry/mcp-server@latest --access-token=TOKEN --host=sentry.example.com

6. 6.Self-hosted without TLS, or without Seer

   Internal deployments that only expose plain HTTP need --insecure-http. Features like Seer may not exist on a self-hosted instance at all; --disable-skills=seer stops the unsupported tools being advertised, which is cleaner than letting them fail at call time.

   shell

   npx @sentry/mcp-server@latest --access-token=TOKEN --host=sentry.internal:9000 --insecure-http --disable-skills=seer

7. 7.Enable the AI-powered search tools

   search_events, search_issues and the other AI-powered search tools translate natural language into Sentry query syntax using an embedded agent, so they need an LLM provider: OpenAI, Azure OpenAI, Anthropic or OpenRouter. Set EMBEDDED_AGENT_PROVIDER explicitly — auto-detection from whichever API keys happen to be present is deprecated and will be removed.

   json

   {
     "mcpServers": {
       "sentry": {
         "command": "npx",
         "args": ["@sentry/mcp-server"],
         "env": {
           "SENTRY_ACCESS_TOKEN": "your-token",
           "EMBEDDED_AGENT_PROVIDER": "openai",
           "OPENAI_API_KEY": "sk-..."
         }
       }
     }
   }

What people use it for

Which one should you use?

Categories

Works With

Frequently Asked Questions

Related Guides