Skip to content

link_issue passes through a misleading 404 when an integration token lists Sentry App installations #2295

Open

Description

@sentry-junior

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.server span has app.access.method=sentry_access (direct Sentry-Bearer token) and no user.id.
  • GET /organizations/{org}/issues/{shortId}/ returned 200. On the region side, GroupDetailsEndpoint made the app.find_installation_by_proxy_user RPC, which Sentry only runs for Sentry App proxy users (src/sentry/auth/access.py:1185, _from_rpc_sentry_app at :1374-1382). So the token is an integration (Sentry App) token.
  • GET https://sentry.io/api/0/organizations/{org}/sentry-app-installations/?per_page=100 returned 404 (span 858fccc96f0fe1d3). The control-silo span stops right after organization.get_access_context_by_slug and never reaches check_object_permissions.
  • Sentry at e495a739f: SentryAppInstallationsBaseEndpoint.convert_args (src/sentry/sentry_apps/api/bases/sentryapps.py:416-422) raises Could not find requested organization when context.member is None for a non-superuser with a user_id. A proxy user is never a member.
  • Toolkit at ca04710: linkAppIssue (packages/mcp-core/src/tools/support/issue-linking/app.ts:311-315) awaits listSentryAppInstallations in a Promise.all and 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_access sessions without a user.id.

Existing work

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.

--

View Session [Sentry]

Activity

  1. linear-code commented on Nov 16, 2026

    @linear-code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions