# Sentry MCP server > Query Sentry errors, issues and traces, and run Seer root-cause analysis from your coding assistant. - Listing: https://mcp.tc/i/sentry - Connect: use the server's own URL `https://mcp.sentry.dev/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Observability & Incidents](https://mcp.tc/c/observability) - Vendor: Sentry - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: - Repository: - Package: npm `@sentry/mcp-server` ## About Connects an AI assistant to the Sentry API so it can look up errors, issues, traces and logs while you debug. It is built for human-in-the-loop coding agents such as Cursor and Claude Code, and includes Seer root-cause analysis on sentry.io. Some search tools translate natural language into Sentry queries. Runs as a hosted streamable HTTP endpoint at https://mcp.sentry.dev/mcp with OAuth sign-in. The endpoint can be scoped by organization and project. A local stdio package (@sentry/mcp-server) runs with npx and a Sentry user token, which suits self-hosted Sentry. The search tools in stdio mode need an LLM provider key. ## What it can do - Look up Sentry issues and errors for debugging - Search errors, traces and logs with natural language - Run Seer root-cause analysis on issues - Scope access to an organization and project - Connect to self-hosted Sentry through the stdio package ## Example prompts - "Show the most recent unresolved errors in my Sentry project." - "Find the root cause of this Sentry issue using Seer." - "Search traces for slow requests on the checkout endpoint." - "What errors started after yesterday's release?" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http sentry https://mcp.sentry.dev/mcp ``` 2. Start Claude Code, type `/mcp`, pick **sentry** and choose **Authenticate**. A browser window opens for the Sentry sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Sentry** and paste this URL: ```url https://mcp.sentry.dev/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Sentry asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.sentry.dev/mcp` and click **Add**. 3. Click **Connect** and sign in when Sentry asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.sentry.dev/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Sentry to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "sentry": { "url": "https://mcp.sentry.dev/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"sentry","type":"http","url":"https://mcp.sentry.dev/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "sentry": { "serverUrl": "https://mcp.sentry.dev/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add sentry --url https://mcp.sentry.dev/mcp codex mcp login sentry ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.sentry] url = "https://mcp.sentry.dev/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http sentry https://mcp.sentry.dev/mcp ``` Then, inside Gemini CLI, run `/mcp auth sentry` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.sentry.dev/mcp`. ## Details - Server version: 0.42.0 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/sentry (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report