Repository navigation
Description
Problem
An agent tried to link a Sentry issue to a Linear issue with link_issue three times, using numeric, short-ID and issue-URL forms. Each call failed with HTTP 404: "Could not find requested organization." Reading the same issue with get_issue_details worked, so the agent couldn't tell what was wrong and kept changing the issue reference (MCP-SERVER-GQW, kind=broken, impact=worked_around, server 0.42.0).
The org exists. The token isn't a member's token. Sentry only lists Sentry App installations for organization members, and link_issue needs that list to find the App's installation UUID.
Evidence
Failing call on 2026-11-16 at 16:02:44 UTC, trace 1ef233a8b788497097715d0d140d0143. There's no mcp.session.id or client.id.
- The MCP
http.serverspan hasapp.access.method=sentry_access(directSentry-Bearertoken) and nouser.id. GET /organizations/{org}/issues/{shortId}/returned 200. On the region side,GroupDetailsEndpointmade theapp.find_installation_by_proxy_userRPC, which Sentry only runs for Sentry App proxy users (src/sentry/auth/access.py:1185,_from_rpc_sentry_appat:1374-1382). So the token is an integration (Sentry App) token.GET https://sentry.io/api/0/organizations/{org}/sentry-app-installations/?per_page=100returned 404 (span858fccc96f0fe1d3). The control-silo span stops right afterorganization.get_access_context_by_slugand never reachescheck_object_permissions.- Sentry at
e495a739f:SentryAppInstallationsBaseEndpoint.convert_args(src/sentry/sentry_apps/api/bases/sentryapps.py:416-422) raisesCould not find requested organizationwhencontext.member is Nonefor a non-superuser with auser_id. A proxy user is never a member. - Toolkit at
ca04710:linkAppIssue(packages/mcp-core/src/tools/support/issue-linking/app.ts:311-315) awaitslistSentryAppInstallationsin aPromise.alland lets the raw 404 through. - This isn't one user. In the last 14 days, sampled spans show 30 404s on this listing call. All 12 traces I checked were
sentry_accesssessions without auser.id.
Existing work
GET /organizations/{org}/sentry-app-installations/returns 404 for internal integration tokens despiteorg:readsentry#128739 reports the same 404 for internal integration tokens. Draft fix(sentry-apps): Let internal integration tokens list their org's installations sentry#129878 lets internal integrations list their own org's installations and returns 403 for published-App tokens.- Inference from code, not tested: even with fix(sentry-apps): Let internal integration tokens list their org's installations sentry#129878, the link
POST /sentry-app-installations/{uuid}/external-issue-actions/checksis_acting_user(request.user, installation.sentry_app.proxy_user_id)for App callers (sentryapps.py:466-468). An internal integration's token would still be refused for the Linear installation. So the MCP should keep a clear error either way. - Not covered by toolkit#2136 (App not installed) or toolkit#1954 (409 URL guard).
Fix
Draft PR to follow: turn the 404 on the installation listing into a UserInputError that says Sentry only lists installations for org members, so integration tokens get this 404, and that linking App issues needs a user token or OAuth sign-in.
Reports
- MCP-SERVER-GQW (2026-11-16)
Report count: 1
via automation evt_905b9c478746fd9deeb853f85ad7441b · Run ID dispatch_6b056fcf1c2c5c748f43774a62ac1591.
--
Activity
linear-code commentedon Nov 16, 2026
MCP-1240