# sentry-mcp

Wires Sentry into your coding assistant so you can dig into errors, traces and performance without leaving the editor. Handy when a bug needs chasing.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed · ★ 944
- Author: getsentry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/getsentry/toolkit/tree/HEAD/packages/mcp-server
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/sentry-mcp

## What it does

The server sits between your assistant and the Sentry API. It targets debugging workflows where a human stays in the loop: the assistant pulls errors, traces and logs, and you decide what to do with them. In Claude it ships as a plugin that adds a `sentry-mcp` subagent, which picks up questions about errors and performance on its own.

Two transports are available. The remote one connects to `https://mcp.sentry.dev/mcp` with no local process. The `stdio` transport runs through `npx @sentry/mcp-server@latest` and mainly serves self-hosted Sentry: add `--host`, and for internal deployments without TLS also `--insecure-http`. You need a Sentry user auth token with scopes for reading org and projects, writing projects and teams, plus `event:write`.

The search tools for errors, traces and logs turn a plain-language query into Sentry's query syntax using an LLM. Without a configured provider those tools stay unavailable; everything else keeps working. Set the provider in `EMBEDDED_AGENT_PROVIDER`, since picking one from API keys alone is deprecated. Point `--host` at a non-`sentry.io` host and the `seer` skill drops out of the default set, because Seer isn't part of self-hosted Sentry; opt back in with `--skills=inspect,seer`.

## Requirements
- Needs: Node.js (commands run via npx)
- Remote server: `https://mcp.sentry.dev/mcp`
- Environment variables: `SENTRY_ACCESS_TOKEN` — keys and tokens: ask the human for the values, never commit them or put them in shared files.
- Works with: Sentry

## Install

### Claude Code (native platform)

1. **Platform CLI: remote server**
```bash
claude mcp add --transport http sentry-mcp https://mcp.sentry.dev/mcp
```

2. **Platform CLI**
```bash
claude mcp add --env SENTRY_ACCESS_TOKEN=<SENTRY_ACCESS_TOKEN> --transport stdio mcp-server -- npx -y @sentry/mcp-server
```
Replace <…> with your own values

### Codex

1. **Platform CLI: remote server**
```bash
codex mcp add mcp-server --url https://mcp.sentry.dev/mcp
```

2. **Platform CLI**
```bash
codex mcp add mcp-server --env SENTRY_ACCESS_TOKEN=<SENTRY_ACCESS_TOKEN> -- npx -y @sentry/mcp-server
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "mcp-server": {
            "url": "https://mcp.sentry.dev/mcp"
        }
    }
}
```
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@sentry/mcp-server"
            ],
            "env": {
                "SENTRY_ACCESS_TOKEN": "<SENTRY_ACCESS_TOKEN>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "mcp-server": {
            "type": "http",
            "url": "https://mcp.sentry.dev/mcp"
        }
    }
}
```
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "mcp-server": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@sentry/mcp-server"
            ],
            "env": {
                "SENTRY_ACCESS_TOKEN": "<SENTRY_ACCESS_TOKEN>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

1. **Platform CLI: remote server**
```bash
gemini mcp add -t http mcp-server https://mcp.sentry.dev/mcp
```

2. **Platform CLI**
```bash
gemini mcp add -e SENTRY_ACCESS_TOKEN=<SENTRY_ACCESS_TOKEN> mcp-server npx -y @sentry/mcp-server
```
Replace <…> with your own values

## When to use it
- read a Sentry stack trace without opening the web UI
- find which errors fire most often in production
- inspect a slow request trace and its timings
- tie a crash to a specific release or environment
- pull the open issue list for a project

## Example prompts
- Show me the latest errors from my Sentry project
- Find the trace for this request and tell me where it's slow
- Which Sentry issues grew after the last release?

## Similar
- [sentry-get-started](https://affpapa.org/en/nevibecode/skills/sentry-get-started.md) — skill · 657 installs
- [sentry-sdk-skill-creator](https://affpapa.org/en/nevibecode/skills/sentry-sdk-skill-creator.md) — skill · 2400 installs
- [Sentry Bug Fixer](https://affpapa.org/en/nevibecode/prompts/sentry-bug-fixer.md) — prompt · ★ 174597
- [sentry-triage](https://affpapa.org/en/nevibecode/plugins/sentry-triage.md) — plugin · ★ 40418
- [sentry](https://affpapa.org/en/nevibecode/skills/brianlovin-sentry.md) — skill · 2800 installs
- [observability](https://affpapa.org/en/nevibecode/skills/observability.md) — skill · 7 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md