# Reported issues for sentry-mcp Pod holds 24 of 179 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [sentry-mcp](/mcp/sentry-mcp). ## Most discussed ### Support API token auth on remote MCP endpoint (not just OAuth) ## Problem The remote MCP endpoint at `https://mcp.sentry.dev/mcp` only supports OAuth 2.0 authentication. This requires a browser-based flow, which makes it unusable in environments that: 1. **Cannot spawn local processes** (e.g., cloud-based IDEs like Claude Code web IDE) — so the stdio transport with `SENTRY_ACCESS_TOKEN` isn't an option 2. **Cannot open a browser** for OAuth — so the remote HTTP endpoint isn't an option either This creates a dead zone where Sentry MCP is completely inacce [Read the thread](https://github.com/getsentry/sentry-mcp/issues/833) · 2026-03-12 · closed · external user · 15 comments ### 0.20.0 fails to communicate to the api due to missing query (self hosted) Does 0.20.0 need a certain server version ? I'm running into constant schema problems when trying to fetch issues... ``` • Called └ sentry.search_events({"organizationSlug":"xyz","regionUrl":"xxyz","naturalLanguageQuery":"latest production errors","limit":5,"response_format":{"type":"json_schema","json_schema": {"name":"response","schema":{"type":"object","properties": {"query":{"type":"string"},"events":{"type":"array","items": {"type":"object"}}},"required": [Read the thread](https://github.com/getsentry/sentry-mcp/issues/623) · 2025-11-02 · closed · external user · 21 comments ### Add OAuth Device Code Flow Support for Headless Environments This may be covered by issue #4, but I wanted to raise it as a separate issue as it is a key workflow for my organization. The current OAuth implementation requires localhost callbacks (http://localhost:5173/oauth/callback), which doesn't work on headless servers or remote development environments where opening a browser locally isn't possible. Problem: - Users on headless machines cannot complete OAuth authentication - SSH port forwarding is a workaround but adds complexity - User [Read the thread](https://github.com/getsentry/sentry-mcp/issues/546) · 2025-09-09 · closed · external user · 13 comments ### Can we have find_issues back? Or, have rawQuery field support. I have a fixed list of queries that I run every morning. Since these queries are fixed, there is no need for OpenAI API calls on them. Alternatively, could we add `rawQuery` field support to the `search_issues` tool alongside the existing `naturalLanguageQuery`? This would pass queries directly to the Sentry API without OpenAI API calls. [Read the thread](https://github.com/getsentry/sentry-mcp/issues/471) · 2025-08-08 · closed · external user · 10 comments ### Unable to get authenticated ### Environment We have an enterprise account, the host name is sentry.io thats where we are signing in ### Steps to Reproduce "Sentry": { "command": "npx", "args": ["mcp-remote@latest", "--access-token=token", "--host="https://employer-name.sentry.io"] } ### Expected Result should be able to be authenticated ### Actual Result [39142] Fatal error: TypeError: Invalid URL at new URL (node:internal/url:818:25) at parseCommandLineArgs (file:///Users/amr.salem/.npm/ [Read the thread](https://github.com/getsentry/sentry-mcp/issues/211) · 2025-05-23 · closed · external user · 25 comments ### Enable or disable list of tools (toolsets) In some cases I only want to use certain tools or I only want users to have access to certain tools. At least when using Roo Code (not sure how other clients work) each tool you add increases bloat in the system prompt so disabling tools also improves efficiency. Other MCP servers implement this with command line arguments or environment variables. For example, the Github MCP server calls them "[toolsets](https://github.com/github/github-mcp-server?tab=readme-ov-file#specifying-toolsets)". [Read the thread](https://github.com/getsentry/sentry-mcp/issues/196) · 2025-05-15 · closed · external user · 9 comments ### Internal Server error when authorizing client with Cursor ### Environment ``` Version: 0.49.6 VSCode Version: 1.96.2 Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50 Date: 2025-04-25T05:07:16.071Z (2 wks ago) Electron: 34.3.4 Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Darwin arm64 24.4.0 ``` ### Steps to Reproduce 1. Add Sentry MCP to `mcp.json` 2. Browser windows open, get an internal server error response 3. Also reproduced by running with `npx mcp-remote https://mcp.sentry.dev/sse list-issues` 4. Tried the auth URL on [Read the thread](https://github.com/getsentry/sentry-mcp/issues/185) · 2025-05-11 · closed · external user · 14 comments ### Add tool to get specific error event information Right now there is a `get_issue_details` tool, which obtains the latest error event: https://github.com/getsentry/sentry-mcp/blob/da9de41fc6b7bac3b4df3543fcbfe0855ed25462/packages/mcp-server/src/tools.ts#L296-L299 There are some cases where we have a specific event id and should be able to get information about that event. Currently that capability does not exist in the MCP server. [Read the thread](https://github.com/getsentry/sentry-mcp/issues/160) · 2025-05-07 · closed · external user · 10 comments ## Most recent ### ChatGPT Business fails to connect to hosted Sentry MCP after OAuth consent ### Environment - Sentry MCP: hosted service at [`https://mcp.sentry.dev/mcp`](https://mcp.sentry.dev/mcp) - Client: ChatGPT Business - Integration: Custom MCP app - Reproduced: Aug 27, 2026 - Sentry MCP version: hosted deployment, so no client-visible version ### Steps to Reproduce 1. Add [`https://mcp.sentry.dev/mcp`](https://mcp.sentry.dev/mcp) as a Custom MCP app in ChatGPT Business. 2. Start the OAuth flow. 3. Approve the requested Sentry permissions. 4. Sentry successfully redirects bac [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1271) · 2026-08-27 · open · external user · 1 comment ### update_issue: resolve in a specific / current semver release ## Summary Expose Sentry’s **Resolved in** release options on `update_issue`, matching the issue-details dropdown: - The current semver release (e.g. `0.1.32`) - Another existing release (`statusDetails.inRelease`) - The next release (already covered by `status='resolvedInNextRelease'`) Today `status='resolved'` is a generic resolve. Any later event from an **older** still-live build (e.g. `0.1.31` while `0.1.32` is the intended fix) immediately marks the issue **regressed**. Agents cannot pe [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1262) · 2026-08-25 · open · external user · 1 comment ### Feature Request: Create a new external issue from a Sentry issue via MCP ## Summary Expose “Create external issue” as an MCP tool (or an `update_issue` action), so an agent can file a **new** ticket in Linear / Jira / GitHub / GitLab / etc. from a Sentry issue and have it linked automatically. This is the half of external-issue support that is **not** covered by PR #1027. Related: - PR #1027 — `feat(issue): Link external issues` (link an **existing** ticket by URL) - #228 — Add action to link JIRA and GitHub issues Filing on behalf of customer. ## Problem Sentry [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1257) · 2026-08-20 · open · external user · 2 comments ### Sentry MCP: get_event_attachment returns an empty body — download fails schema validation, and listing reports SHA1 of the empty string for every attachment ### Environment SaaS (https://sentry.io/) ### Steps to Reproduce Reproduced on org `daniels-sentry-org1` / project `javascript-vue-test` (EU, https://de.sentry.io), event `8c365db20f0845c3a71315a943205d83`, with two attachments of known content: | File | Size | Actual SHA1 | |---|---|---| | one.log (id `858188125`) | 540 B | `223522016c9ef121e912f2462f7f15e22d6e5399` | | two.log (id `858188126`) | 1539 B | `972cc32bff5f16e2891303fe8907e0008931fbfc` | 1. Send an event with two attachments of [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1267) · 2026-08-19 · open · external user · 6 comments ### search_events: nested anyOf in environment schema rejected by Anthropic API (HTTP 400) ## Summary `search_events` declares a nested `anyOf` inside another `anyOf` for its `environment` property. The Anthropic Messages API rejects this construct during tool-schema validation, so **every request fails with HTTP 400 as soon as the Sentry MCP tools are attached** — even when the user never calls `search_events`. The server itself connects fine (handshake, auth, and `tools/call` all succeed when tested directly over stdio). The failure only appears once the tool list reaches the API. [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1250) · 2026-08-14 · closed · external user · 1 comment ### Claude Code plugin 1.3.2: ?utm_source=plugin in MCP URL breaks OAuth (invalid_target) ## Problem The official Claude Code plugin (`getsentry/plugin-claude`) version **1.3.2** changed the MCP server URL in `.claude-plugin/plugin.json` from: ```json "url": "https://mcp.sentry.dev/mcp" ``` to: ```json "url": "https://mcp.sentry.dev/mcp?utm_source=plugin" ``` After the plugin auto-updates to 1.3.2, OAuth authentication fails for every Claude Code user with: ``` invalid_target: The resource parameter does not match this authorization server ``` Filing here because `getsentry/pl [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1247) · 2026-08-14 · open · external user · 1 comment ### execute_sentry_tool breaks host allowlists and approval UX ### Problem Statement `execute_sentry_tool` is an opaque dispatcher over both read and write catalog tools. MCP hosts allowlist and render approvals by top-level tool name, so: * Allowlisting it allowlists mutations (create_project, delete_uptime_monitor, add_issue_note, …). Denying it blocks long-tail reads that aren’t first-class tools. * The approval UI shows execute_sentry_tool with no inner name or arguments. Inner readOnlyHint never reaches the host. ### Solution Brainstorm Please eit [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1254) · 2026-08-14 · open · external user · 2 comments ### Make create_project team optional `create_project` currently requires `teamSlug`, forcing agents and users to understand Sentry teams before creating a project. Until the upstream API provides a stable implied default, sentry-mcp should infer a sensible team locally while preserving explicit team selection. **Current behavior** - `packages/mcp-core/src/tools/catalog/create-project.ts` declares `teamSlug: ParamTeamSlug` and always passes it to `apiService.createProject`. - The tool requires `team:read`, and every documented exam [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1234) · 2026-08-06 · open · outside contributor · 1 comment ### Hosted MCP: agent-backed search tools fail with "Feature Unavailable" (server configuration issue) while non-agent tools work ### Summary On the hosted Sentry MCP server, every agent-backed query tool consistently fails with: ``` **Feature Unavailable** This feature is temporarily unavailable due to a server configuration issue. The service operator has been notified. Please try again later. ``` Non-agent tools in the same authenticated session work fine, so this looks like a problem with the embedded-agent (LLM provider) layer of the hosted service rather than auth or the Sentry API itself. ### Affected tools - [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1226) · 2026-08-04 · open · external user · 1 comment ### get_issue_breadcrumbs should take event ID The current MCP tool, _get_issue_breadcrumbs_, only returns those for the most recent event of an issue. It should take an event ID as an optional argument so we can retrieve the breadcrumbs of multiple events within the same Issue. The reason I need this is so I can do better analysis of categorization of events within a single Issue -- we have found in the past that a single issue can actually point to different unrelated coding issues and I have created a Skill to categorize these into separ [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1222) · 2026-08-03 · closed · external user · 1 comment ### Expose absolute start/end time ranges in search_events and search_issues ## Summary Automated MCP callers need deterministic, closed time windows, but the public input schemas for `search_events` and `search_issues` currently expose only the relative `period` parameter. Please expose optional absolute `start` and `end` parameters for both tools. ## Current behavior `search_events` already has most of the absolute-time plumbing internally: - its embedded-agent output accepts either `{ statsPeriod }` or `{ start, end }` - the API client can forward `start` and `en [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1215) · 2026-07-30 · open · external user · 2 comments ### Migrate low-steering tools to structuredContent Master ticket for migrating data-shaped MCP tools from handwritten markdown to `structuredContent` + `outputSchema`. Prefer tools whose handler is basically fetch → map stable fields → optional limit/cursor note, and whose only steering is presentation (“tell the user X”) or follow-up handles (slug/id/cursor). Skip tools that need markdown to make the result legible, or that return heavy untrusted telemetry. Contract refs: `docs/contributing/tool-responses.md`, existing structured tools (`sear [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1193) · 2026-07-27 · closed · outside contributor · 1 comment ### Hosted MCP OAuth (mcp.sentry.dev) rejects loopback redirect with a port — "Invalid redirect URI" (RFC 8252 §7.3) ## Summary The hosted Sentry MCP OAuth authorization endpoint (`https://mcp.sentry.dev/oauth/authorize`) rejects the OAuth callback used by Claude Code with **"Invalid redirect URI"**. The client registers portless loopback redirect URIs (via its client-ID-metadata document), but the authorization request uses a loopback URI **with a dynamic port** — the standard native/CLI app pattern. Per **RFC 8252 §7.3**, the authorization server must ignore the port when matching loopback (`localhost`/`127 [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1190) · 2026-07-27 · closed · external user · 3 comments ### CIMD + loopback redirect URIs: exact-match check in `POST /oauth/authorize` rejects native clients with "Invalid redirect URI" ### Summary Since 29d00ac ("feat(cloudflare): Bump oauth provider and enable CIMD (#1183)"), OAuth against `https://mcp.sentry.dev/mcp` fails for native/CLI clients that use ephemeral loopback ports. The consent dialog renders correctly and displays the redirect URI, but submitting the approval returns **400 "Invalid redirect URI"**. The cause is the redirect URI check in `POST /oauth/authorize`, which uses exact array membership and therefore does not honour RFC 8252 §7.3 loopback port flexi [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1189) · 2026-07-27 · closed · outside contributor · 2 comments ### fix(mcp-core): ensure newline after formatted issue content ## Bug In `formatIssueOutput`, `event.formatted.content` is appended without guaranteeing a trailing newline. When the shared formatter content does not end with `\n`, later headers such as `## Seer Analysis` and `## Response Notes` land on the same line and break markdown structure agents rely on. Verified on `shayna-ch/format-mcp` (PR #1162): ``` last line without trailing newline## Seer Analysis ``` ## Fix Ensure a trailing newline after appending `event.formatted.content`, plus a regres [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1168) · 2026-07-20 · closed · external user · 2 comments ### Include resolved code-mapping / stacktrace GitHub links in issue payloads ### Problem Statement Sentry UI correctly shows the “Open on GitHub” link for stack frames. However, this information is not exposed in the Issue/Event API payload. This becomes a limitation for API consumers such as MCP. The MCP server can only return what is available in the issue payload, so AI agents cannot navigate directly to the corresponding source code even though the Sentry UI already has that information. From what I understand, the UI performs an additional lookup using the stack [Read the thread](https://github.com/getsentry/sentry-mcp/issues/1157) · 2026-07-15 · closed · external user · 8 comments The remaining reports are on [the project's issue tracker](https://github.com/getsentry/sentry-mcp/issues).