{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "sentry", "Name": "Sentry", "CanonicalUrl": "https://askpod.ai/mcp/sentry/issues", "ServerUrl": "https://askpod.ai/mcp/sentry", "IssueTotal": 182, "Held": 24, "Issues": [ { "Title": "Unable to get authenticated", "Excerpt": "### Environment\n\nWe have an enterprise account, the host name is sentry.io thats where we are signing in\n\n### Steps to Reproduce\n\n \"Sentry\": {\n \"command\": \"npx\",\n \"args\": [\"mcp-remote@latest\", \"--access-token=token\", \"--host=\"https://employer-name.sentry.io\"]\n }\n\n### Expected Result\n\nshould be able to be authenticated\n\n### Actual Result\n\n[39142] Fatal error: TypeError: Invalid URL\n at new URL (node:internal/url:818:25)\n at parseCommandLineArgs…", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/211", "PublishedAt": "2025-05-23T10:57:11.000Z", "State": "closed", "Comments": 25, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "0.20.0 fails to communicate to the api due to missing query (self hosted)", "Excerpt": "Does 0.20.0 need a certain server version ?\n\nI'm running into constant schema problems when trying to fetch issues...\n\n```\n• Called\n └ sentry.search_events({\"organizationSlug\":\"xyz\",\"regionUrl\":\"xxyz\",\"naturalLanguageQuery\":\"latest production\n errors\",\"limit\":5,\"response_format\":{\"type\":\"json_schema\",\"json_schema\":\n {\"name\":\"response\",\"schema\":{\"type\":\"object\",\"properties\":\n {\"query\":{\"type\":\"string\"},\"events\":{\"type\":\"array\",\"items\":…", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/623", "PublishedAt": "2025-11-02T21:26:32.000Z", "State": "closed", "Comments": 21, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Support API token auth on remote MCP endpoint (not just OAuth)", "Excerpt": "## Problem\n\nThe 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:\n\n1. **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\n2. **Cannot open a browser** for OAuth — so the remote HTTP endpoint isn't an option either\n\nThis creates a dead zone where Sentry MCP is completely…", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/833", "PublishedAt": "2026-03-12T19:59:47.000Z", "State": "closed", "Comments": 15, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Internal Server error when authorizing client with Cursor", "Excerpt": "### Environment\n```\nVersion: 0.49.6\nVSCode Version: 1.96.2\nCommit: 0781e811de386a0c5bcb07ceb259df8ff8246a50\nDate: 2025-04-25T05:07:16.071Z (2 wks ago)\nElectron: 34.3.4\nChromium: 132.0.6834.210\nNode.js: 20.18.3\nV8: 13.2.152.41-electron.0\nOS: Darwin arm64 24.4.0\n```\n\n### Steps to Reproduce\n\n1. Add Sentry MCP to `mcp.json`\n2. Browser windows open, get an internal server error response\n3. Also reproduced by running with `npx mcp-remote https://mcp.sentry.dev/sse list-issues`\n4. Tried the auth URL…", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/185", "PublishedAt": "2025-05-11T10:40:58.000Z", "State": "closed", "Comments": 14, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Add OAuth Device Code Flow Support for Headless Environments", "Excerpt": "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.\n\nThe current OAuth implementation requires localhost callbacks\n (http://localhost:5173/oauth/callback), which doesn't work on headless servers or remote\n development environments where opening a browser locally isn't possible.\n\n Problem:\n - Users on headless machines cannot complete OAuth authentication\n - SSH port forwarding is a workaround but adds complexity\n -…", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/546", "PublishedAt": "2025-09-09T19:41:00.000Z", "State": "closed", "Comments": 13, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Can we have find_issues back? Or, have rawQuery field support.", "Excerpt": "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.\n\nAlternatively, 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.", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/471", "PublishedAt": "2025-08-08T19:20:42.000Z", "State": "closed", "Comments": 10, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Add tool to get specific error event information", "Excerpt": "Right now there is a `get_issue_details` tool, which obtains the latest error event:\nhttps://github.com/getsentry/sentry-mcp/blob/da9de41fc6b7bac3b4df3543fcbfe0855ed25462/packages/mcp-server/src/tools.ts#L296-L299\n\nThere 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.", "SourceUrl": "https://github.com/getsentry/sentry-mcp/issues/160", "PublishedAt": "2025-05-07T12:07:53.000Z", "State": "closed", "Comments": 10, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Failed to authenticate with the Sentry's MCP server over SSO", "Excerpt": "### Environment\n\nSaaS (https://sentry.io/)\n\n### Steps to Reproduce\n\nHey, I'm attempting to work with the official Sentry MCP server and failing to authenticate it. I suspect it is because my org uses SSO to authenticate to Sentry's services, but cannot confirm that.\n\n## Steps to reproduce:\n\nLogin to Sentry with Okta\n\n\"Image\"\n\nAuth\n\n