---
title: "Sentry MCP Server: Errors, Traces and Seer in Your Editor"
url: "https://mcpshelf.co/servers/sentry"
description: "Sentry's own MCP server brings issues, stack traces, logs, traces and Seer root-cause analysis into Claude Code or Cursor. Remote setup, tokens, skills."
updated: "2026-11-10"
site: "MCP Shelf"
---

# Sentry MCP

> Sentry issues, stack traces, traces and Seer fixes inside your coding agent.

Source: https://mcpshelf.co/servers/sentry  
Markdown: https://mcpshelf.co/servers/sentry.md  
Generated: 2026-11-22T13:57:56.721Z

## Facts

- **Name:** Sentry MCP
- **Tagline:** Sentry issues, stack traces, traces and Seer fixes inside your coding agent.
- **Description:** Sentry MCP is Sentry's official server that lets a coding agent read issues, stack traces, logs, traces and replays from Sentry and ask Seer, Sentry's AI debugger, for a root cause and fix.
- **Repository:** https://github.com/getsentry/toolkit
- **Install:** `claude mcp add --transport http sentry https://mcp.sentry.dev/mcp`
- **Server URL:** https://mcp.sentry.dev/mcp
- **Transport:** Streamable HTTP (remote)
- **Auth:** No required keys or settings listed
- **Tools exposed:** 48: `analyze_issue_with_seer`, `find_alert_rules`, `find_dashboards`, `find_dropped_events`, `find_metric_monitors`, `find_monitors`, `find_organizations`, `find_projects`, `find_releases`, `find_teams`, `find_uptime_monitors`, `get_agent_conversation_details`, `get_alert_options`, `get_alert_rule`, `get_dashboard_details`, `get_doc`, `get_event_attachment`, `get_event_stacktrace`, `get_issue_activity`, `get_issue_breadcrumbs`, `get_issue_details`, `get_issue_tag_values`, `get_issue_user_reports`, `get_latest_base_snapshot`, `get_metric_monitor_details`, `get_monitor_details`, `get_profile`, `get_profile_details`, `get_release_details`, `get_replay_details`, `get_sentry_resource`, `get_snapshot`, `get_snapshot_image`, `get_span_details`, `get_trace_details`, `get_uptime_monitor_details`, `search_agent_conversations`, `search_docs`, `search_errors`, `search_events`, `search_issue_events`, `search_issues`, `search_logs`, `search_metrics`, `search_profiles`, `search_replays`, `search_traces`, `whoami`
- **Category:** Developer tools (https://mcpshelf.co/categories/developer-tools)
- **Stats:** 949 GitHub stars, 77.9K downloads a week, last commit 28 Oct 2026, 0 upvotes on MCP Shelf
- **Install check:** Needs your setup first
- **Listed:** 2026-11-10
- **Page updated:** 2026-11-10

## Full description

### What is Sentry MCP?

**Sentry MCP is Sentry's official server that lets a coding agent read issues, stack traces, logs, traces and replays from Sentry and ask Seer, Sentry's AI debugger, for a root cause and fix.**

Sentry built this server for coding agents rather than as a general admin tool. Paste an issue link or ask what broke and the assistant can open the issue, read the stack trace, breadcrumbs and tags, search errors, logs, spans and replays, and ask Seer, Sentry's own AI debugger, for a root cause and a suggested fix. That is usually enough to go from an alert to a patch without leaving the editor.

It runs as a remote server at mcp.sentry.dev that signs in with OAuth. Tools come in skill groups: inspecting and Seer are on by default, while triage (resolving and assigning issues) and project management (projects, DSNs, monitors, alert rules) have to be granted. A stdio package exists too, mainly for self-hosted Sentry.

|  |  |
| --- | --- |
| Made by | Sentry (getsentry/toolkit) |
| GitHub | https://github.com/getsentry/toolkit |
| Licence | FSL-1.1-ALv2 |
| GitHub stars | 949 |
| Downloads | 77.9K a week |
| Last commit | 28 Oct 2026 |
| Tools | 48 |
| Runs on | Hosted |
| Install check | Needs your setup first |
| Category | [Developer tools](https://mcpshelf.co/categories/developer-tools) |
| Works with | Claude Code, Cursor, Claude Desktop, VS Code, Codex, Windsurf, ChatGPT |
| Setup checked | 10 Nov 2026 |
| Page updated | 10 Nov 2026 |

**Our check:** It needs something our Linux test machine does not have (an account, a desktop app, a Mac or a running service), so on 10 Nov 2026 we read its tools from the source code instead of running this config. The repository moved from getsentry/sentry-mcp to getsentry/toolkit, which also holds the Sentry CLI. The stdio package is @sentry/mcp-server on npm, published from that repository.

#### Try asking Sentry MCP

- "What are the top unresolved errors in my project this week?"
- "Show me the stack trace for this issue and suggest a fix: <issue link>"
- "Which release introduced this error?"

#### MCP Shelf take

> Sentry needs something our Linux test machine does not have (an account, an app or a service), so on 10 Nov 2026 we read its source and counted 48 tools. 47 of the 48 only read; the other 1 can change things. It sits 23rd of 24 in its category on our shelf by GitHub stars (949, with 77.9K downloads a week).

— MCP Shelf tests (numbers from our own runs), tested on 10 Nov 2026

### What tools does Sentry MCP have?

We listed 48 tools on 10 Nov 2026. 47 only read; the rest can change things or run commands.

| Tool | Kind | What it is for |
| --- | --- | --- |
| `analyze_issue_with_seer` | changes | Asks Seer for a root-cause analysis of an issue and a suggested code fix. |
| `find_alert_rules` | reads | Lists alert rules. |
| `find_dashboards` | reads | Lists dashboards. |
| `find_dropped_events` | reads |  |
| `find_metric_monitors` | reads | Lists metric monitors. |
| `find_monitors` | reads | Lists cron monitors. |
| `find_organizations` | reads | Lists the organisations you can see, with the slug and region other tools need. |
| `find_projects` | reads | Lists or searches the projects in an organisation. |
| `find_releases` | reads | Lists releases for a project. |
| `find_teams` | reads |  |
| `find_uptime_monitors` | reads | Lists uptime monitors. |
| `get_agent_conversation_details` | reads |  |
| `get_alert_options` | reads |  |
| `get_alert_rule` | reads |  |
| `get_dashboard_details` | reads |  |
| `get_doc` | reads | Reads one Sentry docs page. |
| `get_event_attachment` | reads |  |
| `get_event_stacktrace` | reads | Returns an event's stack trace on its own. |
| `get_issue_activity` | reads | Lists an issue's history: status changes, assignments and notes. |
| `get_issue_breadcrumbs` | reads | Shows the breadcrumbs that led up to an error. |
| `get_issue_details` | reads | Reads one issue: its error, latest event, stack trace and tags. |
| `get_issue_tag_values` | reads | Shows how an issue spreads across a tag, such as browser or release. |
| `get_issue_user_reports` | reads | Reads the feedback users sent with an issue. |
| `get_latest_base_snapshot` | reads |  |
| `get_metric_monitor_details` | reads |  |
| `get_monitor_details` | reads |  |
| `get_profile` | reads |  |
| `get_profile_details` | reads | Reads one profile. |
| `get_release_details` | reads | Reads one release, with its commits and new issues. |
| `get_replay_details` | reads | Reads one session replay's summary. |
| `get_sentry_resource` | reads | Opens anything from a Sentry link or id: an issue, event, trace, replay and so on. |
| `get_snapshot` | reads |  |
| `get_snapshot_image` | reads |  |
| `get_span_details` | reads | Reads one span. |
| `get_trace_details` | reads | Reads a whole trace with its spans. |
| `get_uptime_monitor_details` | reads |  |
| `search_agent_conversations` | reads |  |
| `search_docs` | reads | Searches the Sentry documentation. |
| `search_errors` | reads | Searches error events, with counts and trends, from a plain-English question. |
| `search_events` | reads |  |
| `search_issue_events` | reads | Lists the individual events inside one issue. |
| `search_issues` | reads | Finds issues from a plain-English description, such as unresolved errors in checkout this week. |
| `search_logs` | reads | Searches log lines the same way. |
| `search_metrics` | reads | Queries trace metrics. |
| `search_profiles` | reads | Finds profiling data. |
| `search_replays` | reads | Finds session replays. |
| `search_traces` | reads | Searches spans and traces, for questions such as the slowest endpoints today. |
| `whoami` | reads | Shows which Sentry user the session is signed in as. |

#### Tool groups

| Group | Covers |
| --- | --- |
| `inspect (on by default)` | Read-only: issues, events, stack traces, breadcrumbs, traces, spans, logs, replays, profiles, releases, dashboards, monitors, alert rules and the Sentry docs. |
| `seer (on by default on sentry.io)` | analyze_issue_with_seer, Sentry's AI root-cause analysis and fix suggestions. Left out by default on self-hosted Sentry, which has no Seer. |
| `triage (off until you grant it)` | update_issue, notes, and linking or unlinking issues to external trackers. |
| `project-management (off until you grant it)` | Create and change projects, teams, DSNs, cron, uptime and metric monitors, and alert rules. |

### How do I install Sentry MCP?

#### Install steps from the Sentry MCP README

Its licence does not let us copy the README; read the install steps on GitHub: https://github.com/getsentry/toolkit#readme

#### What you need first

- A Sentry account on sentry.io, or a self-hosted Sentry with a user auth token
- For the natural-language search tools on stdio only: an OpenAI, Anthropic or OpenRouter key

#### Claude Code

Where: Your terminal, in the project folder

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

Sentry also ships a Claude Code plugin with a sentry-mcp subagent that Claude hands Sentry questions to: claude plugin marketplace add getsentry/sentry-mcp, then claude plugin install sentry-mcp@sentry-mcp.

#### Cursor

Where: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

```json
{
  "mcpServers": {
    "sentry": {
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}
```

Cursor opens Sentry's sign-in page the first time it connects. Pick the organisation and the skills to grant there.

#### Claude Desktop

Where: Customize → Connectors → add a custom connector

```
https://mcp.sentry.dev/mcp
```

Paste the URL and sign in if asked. Custom connectors depend on your plan.

#### VS Code

Where: .vscode/mcp.json in your project

```json
{
  "servers": {
    "sentry": {
      "type": "http",
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}
```

#### Codex

Where: ~/.codex/config.toml, shared by the Codex CLI, IDE extension and ChatGPT desktop app

```
[mcp_servers.sentry]
url = "https://mcp.sentry.dev/mcp"
```

Or run: `codex mcp add sentry --url https://mcp.sentry.dev/mcp`, then `codex mcp login sentry` if it asks you to sign in.

#### Windsurf

Where: ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "sentry": {
      "serverUrl": "https://mcp.sentry.dev/mcp"
    }
  }
}
```

#### ChatGPT

Where: chatgpt.com/plugins → + → Add custom MCP server

```
https://mcp.sentry.dev/mcp
```

Paste the URL as the server address, choose OAuth if it asks you to sign in, create it as a plugin, then install it before using it in a chat. Workspace admins can block custom servers.

Your client opens a Sentry sign-in in the browser, where you pick the organisation and the skills to grant. For self-hosted Sentry, run npx @sentry/mcp-server@latest with SENTRY_AUTH_TOKEN and SENTRY_HOST instead.

Checked against the project's own install docs on 10 Nov 2026: https://github.com/getsentry/toolkit#readme, https://mcp.sentry.dev, https://www.npmjs.com/package/@sentry/mcp-server

### How do I configure Sentry MCP?

| Setting | Kind | Required | What it does |
| --- | --- | --- | --- |
| `https://mcp.sentry.dev/mcp` | config | no | The hosted server. It signs in with OAuth, where you choose the organisation and the skills to grant. |
| `?skills= and ?disable-skills=` | config | no | Query parameters on the hosted URL that narrow which skill groups load. Example: `https://mcp.sentry.dev/mcp?skills=inspect,triage` |
| `Authorization: Sentry-Bearer` | config | no | Header for passing a Sentry API token to the hosted server instead of OAuth. Kept apart from Bearer, which is for OAuth tokens. Example: `Authorization: Sentry-Bearer YOUR_SENTRY_TOKEN` |
| `SENTRY_AUTH_TOKEN` | env | no | A user auth token for the stdio package, with org:read, project:read, project:write, team:read, team:write and event:write. Optional after npx @sentry/mcp-server@latest auth login. |
| `SENTRY_HOST` | env | no | Your self-hosted Sentry's hostname for the stdio package. Setting it also drops the seer skill. Use SENTRY_URL with http:// for an internal server without TLS. Example: `sentry.example.com` |
| `EMBEDDED_AGENT_PROVIDER` | env | no | Which LLM the stdio package uses to turn plain-English searches into Sentry queries: openai, azure-openai, anthropic or openrouter, with the matching API key. Without one, the search_* tools are missing. Example: `anthropic` |
| `MCP_SKILLS and MCP_DISABLE_SKILLS` | env | no | Choose skill groups for the stdio package, or --skills and --disable-skills on the command line. Example: `inspect,seer` |

### What can Sentry MCP read and change?

**It can read**

- Issues, events, stack traces, breadcrumbs and user feedback
- Traces, spans, logs, metrics, replays and profiles
- Releases, dashboards, monitors, alert rules and project settings

**It can change**

- Issue status, assignees and notes, with the triage skill
- Projects, teams, DSNs, monitors and alert rules, with project management
- Starts Seer analyses, which count against your Seer usage

**Safer setup:** Grant only inspect, plus seer if you use it, when you sign in. Add triage or project management later, once you want the agent to change things.

### Good for

- Going from a Sentry alert to a fix in the same session
- Asking for errors, slow spans or logs in plain English instead of Sentry query syntax
- Running Seer root-cause analysis on an issue from your coding agent

### Sentry MCP not working? Common fixes

**Rate Limited messages**
Sentry's API limits calls per second, and agents hit them by running many Sentry tools in parallel. The server retries on its own; if it still fails, ask the agent to run calls one at a time.

**search_errors, search_logs and the other search tools are missing on stdio**
They need an LLM provider. Set EMBEDDED_AGENT_PROVIDER and that provider's API key in env.

**OAuth fails in the MCP Inspector on 127.0.0.1**
Open the Inspector on localhost instead, for example http://localhost:6274.

**Seer is missing on self-hosted Sentry**
Self-hosted Sentry has no Seer, so setting SENTRY_HOST drops it. If your deployment does run Seer, add --skills=inspect,seer.

**The server warns about --access-token**
That option is deprecated. Use SENTRY_AUTH_TOKEN, or sign in once with npx @sentry/mcp-server@latest auth login.

### What are the alternatives to Sentry MCP?

| Server | What it does | Tools | Runs on | Licence | Stars |
| --- | --- | --- | --- | --- | --- |
| [Sentry MCP](https://mcpshelf.co/servers/sentry) | Sentry issues, stack traces, traces and Seer fixes inside your coding agent. | 48 | Hosted | FSL-1.1-ALv2 | 949 |
| [Microsoft Learn MCP](https://mcpshelf.co/servers/microsoft-learn) | Official Microsoft docs and code samples for your assistant, free and with no sign-in. | 3 | Hosted | CC-BY-4.0 | 2K |
| [Postman MCP Server](https://mcpshelf.co/servers/postman) | Your Postman workspaces, collections, specs and mocks, from inside the editor. | 42 | Hosted | Apache-2.0 | 325 |
| [Desktop Commander](https://mcpshelf.co/servers/desktop-commander) | A terminal, file search and surgical file edits for your assistant. | 25 | Your computer | MIT | 10.2K |
| [Serena](https://mcpshelf.co/servers/serena) | IDE-style "find symbol" and "edit symbol" for an agent, backed by language servers. | 3 (REPL) | Your computer | GPL-3.0 | 30.8K |
| [Context7](https://mcpshelf.co/servers/context7) | Pulls current, version-specific library docs into the conversation. | 2 | Your computer or hosted | MIT | 63.8K |

### Sentry MCP FAQ

#### Is Sentry MCP official?

Yes. Sentry builds it in the getsentry/toolkit repository, alongside the Sentry CLI, and runs the hosted server at mcp.sentry.dev. The stdio version is the @sentry/mcp-server package on npm.

#### How do I add Sentry MCP to Claude Code?

Run claude mcp add --transport http sentry https://mcp.sentry.dev/mcp, then /mcp to sign in. Or install Sentry's plugin, which adds a subagent for Sentry questions: claude plugin install sentry-mcp@sentry-mcp after adding the getsentry/sentry-mcp marketplace.

#### Does Sentry MCP work with self-hosted Sentry?

Yes, through the stdio package. Run npx @sentry/mcp-server@latest with SENTRY_HOST set to your server and SENTRY_AUTH_TOKEN, or sign in with auth login. Seer is left out, as self-hosted Sentry does not include it.

#### Can the agent change things in Sentry?

Only if you grant it. Inspect and Seer are the default skills. Resolving and assigning issues needs triage, and creating projects, DSNs, monitors or alert rules needs project management.

#### What is Seer?

Sentry's AI debugger. analyze_issue_with_seer asks it to find the root cause of an issue and propose a fix, which your coding agent can then apply.

#### Why does the local version need an OpenAI or Anthropic key?

The search tools take plain-English questions and use an LLM to turn them into Sentry query syntax. The hosted server handles that for you; with stdio you supply the provider and key.

#### What licence is Sentry MCP under?

The Functional Source License 1.1, which turns into Apache 2.0 after two years. You can use and self-host it freely, but not offer it as a competing commercial service.

#### What does Sentry MCP cost?

The server itself is free to use with any Sentry plan. Seer is a paid Sentry feature, so analyses count against your Seer usage.

#### How do I add Sentry MCP to Cursor?

In ~/.cursor/mcp.json, or .cursor/mcp.json for one project, add an entry named sentry with the URL https://mcp.sentry.dev/mcp. Cursor opens Sentry's sign-in page the first time it connects. Pick the organisation and the skills to grant there.

#### Can I use Sentry MCP in VS Code?

Yes, through GitHub Copilot. In .vscode/mcp.json, add a server named sentry with type http and the URL https://mcp.sentry.dev/mcp. Then switch Copilot Chat to Agent mode to use its tools.

#### Does Sentry MCP work with Codex?

Yes. Run codex mcp add sentry --url https://mcp.sentry.dev/mcp in a terminal, or add an [mcp_servers.sentry] table to ~/.codex/config.toml, which the Codex CLI and IDE extension share. Then codex mcp login sentry if it asks you to sign in.

Full docs on GitHub: https://github.com/getsentry/toolkit

## Notes for agents

Fetch these instead of parsing the HTML page:

- llms.txt: https://mcpshelf.co/llms.txt
- llms-full.txt: https://mcpshelf.co/llms-full.txt
- ai.txt: https://mcpshelf.co/ai.txt
- Full catalog (.md): https://mcpshelf.co/catalog.md
- API spec: https://mcpshelf.co/openapi.json
- MCP server: https://mcpshelf.co/mcp
- MCP manifest: https://mcpshelf.co/.well-known/mcp.json
- Developer docs: https://mcpshelf.co/developers

MCP endpoint (Streamable HTTP, no key): https://mcpshelf.co/mcp. REST API: https://mcpshelf.co/api/v1.

