getsentry/sentry-mcp

This repository contains the Sentry CLI, the Sentry MCP server, and shared
packages. For the CLI, see the CLI guide and the published
documentation at . The documentation index
covers both products and shared contributor guidance.
Sentry MCP
Sentry's MCP service is primarily designed for human-in-the-loop coding agents. Our tool selection and priorities are focused on developer workflows and debugging use cases, rather than providing a general-purpose MCP server for all Sentry functionality.
This remote MCP server acts as middleware to the upstream Sentry API, optimized for coding assistants like Cursor, Claude Code, and similar development tools. It's based on Cloudflare's work towards remote MCPs.
Getting Started
You'll find everything you need to know by visiting the deployed service in production:
If you're looking to contribute, learn how it works, or to run this for self-hosted Sentry, continue below.
Claude Code Plugin
Install as a Claude Code plugin for automatic subagent delegation:
This provides a sentry-mcp subagent that Claude automatically delegates to when you ask about Sentry errors, issues, traces, or performance.
For forward-looking tool variants and features:
Stdio vs Remote
While this repository is focused on acting as an MCP service, we also support a stdio transport. This is still a work in progress, but is the easiest way to adapt run the MCP against a self-hosted Sentry install.
**Note:** The AI-powered search tools (search_errors, search_traces, search_logs, search_issues, etc.) require an LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter). These tools use natural language processing to translate queries into Sentry's query syntax. Without a configured provider, these specific tools will be unavailable, but all other tools will function normally.
To utilize the stdio transport, you'll need to create an User Auth Token in Sentry with the necessary scopes. As of writing this is:
Launch the transport:
Need to connect to a self-hosted deployment? Add --host (hostname
only, e.g. --host=sentry.example.com ) when you run the command.
For isolated internal deployments that only expose plain HTTP, also add
--insecure-http .
Seer is not part of self-hosted Sentry, so the seer skill is left out of the
default skill set whenever --host points at a non-sentry.io host. If your
self-hosted deployment does run Seer, opt back in explicitly:
You can also disable any other skill to prevent unsupported tools from being
exposed:
For self-hosted instances without TLS:
Remote with an Explicit Sentry Token
Remote clients that support custom HTTP headers can pass an upstream Sentry API
token directly to the Cloudflare transport:
Sentry-Bearer is intentionally separate from Bearer: Bearer is reserved
for MCP OAuth access tokens. With Sentry-Bearer, the worker does not store,
validate, exchange, or refresh the upstream token. It forwards the token through
the same Sentry API calls used by OAuth-backed sessions, and the client or
upstream provider remains responsible for token lifetime and refresh.
Direct remote auth defaults to all active MCP skills. You can narrow the exposed
tools with ?skills=inspect,triage or ?disable-skills=seer.
Environment Variables
**Important:** Always set EMBEDDED_AGENT_PROVIDER to explicitly specify your LLM provider. Auto-detection based on API keys alone is deprecated and will be removed in a future release. See docs/operations/embedded-agents.md for detailed configuration options.