Sentry MCP logo

Sentry MCP

by getsentry

Connects coding agents to Sentry for investigating errors, issues, traces, and performance data through MCP.

Install Sentry MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "getsentry-sentry-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server@latest"
      ],
      "env": {
        "SENTRY_ACCESS_TOKEN": "YOUR_VALUE_HERE",
        "EMBEDDED_AGENT_PROVIDER": "YOUR_VALUE_HERE",
        "OPENAI_API_KEY": "YOUR_VALUE_HERE",
        "ANTHROPIC_API_KEY": "YOUR_VALUE_HERE",
        "OPENROUTER_API_KEY": "YOUR_VALUE_HERE",
        "OPENROUTER_MODEL": "YOUR_VALUE_HERE",
        "OPENROUTER_REASONING_EFFORT": "YOUR_VALUE_HERE",
        "SENTRY_HOST": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @sentry/mcp-server@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The getsentry/sentry-mcp MCP server connects coding assistants to Sentry through a remote MCP service or a local stdio process. It forwards agent requests to the Sentry API and focuses on developer workflows such as investigating errors, issues, traces, and performance. AI-assisted search tools translate natural-language requests into Sentry query syntax through a configured LLM provider. Use it when an agent needs authenticated access to Sentry data, including self-hosted deployments.

Use cases

  • Investigate Sentry errors from a coding assistant
  • Search Sentry issues with natural-language queries
  • Review traces and performance data during debugging
  • Connect an agent to a self-hosted Sentry instance
  • Delegate Sentry investigations to a Claude Code subagent

Key features

  • Remote MCP access through mcp.sentry.dev
  • Local stdio transport for Sentry
  • Error, issue, trace, and performance investigation
  • AI-assisted event and issue search
  • Self-hosted Sentry host override
  • Selective skill disabling

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

20/20 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @sentry/mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars947Stargazers on the source repository.
npm downloads298kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Sentry MCP works

What getsentry/sentry-mcp MCP server does

The getsentry/sentry-mcp MCP server exposes Sentry-focused tools for coding assistants. Its intended use is human-guided debugging rather than broad coverage of every Sentry feature. Agents can use it to investigate application errors, Sentry issues, traces, and performance information during development and incident analysis.

The service is available as a hosted endpoint at https://mcp.sentry.dev/mcp. The repository also provides a stdio transport for local use, including connections to self-hosted Sentry installations. Claude Code can install the repository as a plugin that supplies a Sentry-specific subagent, while Cursor and similar development tools can connect through MCP.

How it works

The remote deployment acts as middleware between an MCP client and the upstream Sentry API. A client can authenticate through the hosted service or pass an upstream Sentry token in the Sentry-Bearer header. That header is separate from the standard Bearer mechanism used for MCP OAuth access tokens, and the service forwards the supplied Sentry token rather than managing its refresh lifecycle.

The local mode runs through the @sentry/mcp-server npm package. It uses a Sentry user auth token and targets Sentry SaaS by default. Set a host override when connecting to a self-hosted installation. Plain-HTTP internal deployments require the insecure HTTP option.

The getsentry/sentry-mcp MCP server includes AI-assisted search functions such as search_events and search_issues. These functions require a configured provider from OpenAI, Azure OpenAI, Anthropic, or OpenRouter because they convert natural-language searches into Sentry query syntax. Without a provider, those particular functions are unavailable, while other tools continue to work.

Setup and configuration

For stdio use, create a Sentry user auth token with these documented scopes: org:read, project:read, project:write, team:read, team:write, and event:write. Start the server with npx -y @sentry/mcp-server@latest and provide the token through the command option or SENTRY_ACCESS_TOKEN.

Set SENTRY_HOST only for self-hosted Sentry. Use MCP_DISABLE_SKILLS to hide selected skill groups, such as seer, when the target installation does not support them. AI search also needs EMBEDDED_AGENT_PROVIDER and the corresponding provider credential. OpenRouter supports optional model and reasoning-effort settings.

The hosted service can receive an explicit token through a custom HTTP header. Its endpoint can also be narrowed with skills or disable-skills query parameters, including examples such as inspect, triage, and seer.

Limitations and notes

The project describes stdio support as still in progress. Some features, including Seer, may not exist on self-hosted Sentry instances. The getsentry/sentry-mcp MCP server therefore supports disabling unsupported skills rather than assuming every deployment exposes the same tools.

Remote token forwarding leaves token lifetime and refresh responsibility with the client or upstream provider. AI-powered search is conditional on external LLM configuration and is not available when no supported provider is configured. The repository also includes development and testing commands, but those are for contributors rather than end-user installation.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sentry MCP

For local stdio use, run `npx -y @sentry/mcp-server@latest` and provide a Sentry user auth token. The hosted service is available at `https://mcp.sentry.dev/mcp`.

Run the stdio package with a Sentry access token and set `SENTRY_HOST`, or pass the `--host` option. Add `--insecure-http` for an internal deployment that exposes only plain HTTP.

AI-powered tools such as `search_events` and `search_issues` require an LLM provider and its credentials. Configure `EMBEDDED_AGENT_PROVIDER` with OpenAI, Azure OpenAI, Anthropic, or OpenRouter settings.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSentry MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/getsentry-sentry-mcp?style=directory)](https://allmcps.com/mcp/getsentry-sentry-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/getsentry-sentry-mcp"><img src="https://allmcps.com/api/badge/getsentry-sentry-mcp?style=directory" alt="Sentry MCP on AllMCPs" /></a>