[sentry-junior]

Task 8.2 of the unify-sentry-api-layer change (#1669): the MCP's issue and event reads in SentryApiService now call @sentry/api operations instead of building requestJSON(apiPath...) URLs by hand.

The calls go through the existing sdkClient() bridge, the same one the organization, team, and project lists use. The SDK only builds the path and query. The MCP still owns auth, host and region routing, retries, the ApiError mapping (HTTP status kept), and Zod parsing. The bridge also rejects any URL that doesn't match the apiPath result, so path-traversal protection is unchanged. When 6.1 lands, that bridge is the one place to swap in the injected fetch. Tool output and snapshots don't change.

Events

• getEventForIssue → getOrganizationIssueEvent. Since 0.421.0, @sentry/api sends collapse=adjacentEvents by default (feat(client): Skip adjacent-event lookups by default in getOrganizationIssueEvent sentry-api-schema#112, server side perf(issues): Add collapse=adjacentEvents to group event details sentry#129094), so the hand-added ?collapse=adjacentEvents from perf(api): Skip adjacent-event lookups on event details #1705 is gone. The existing request test still checks the parameter for latest, oldest, recommended, and a hex ID. The generated event_id type lists only the three aliases, so a hex ID needs a narrow cast.
• listEventsForIssue → listOrganizationIssueEvents. It no longer sends sort. The generated operation has no such parameter, and GroupEventsEndpoint ignores it: results always come back -timestamp first. search_issue_events still uses its sort for the Discover link. Tests now check that link instead of the ignored query parameter.
• listEventAttachments → listProjectEventAttachments. getEventAttachment reuses it for the metadata lookup.
• The MCP never calls the project event details endpoint, so there was no explicit collapse to keep. getProjectEvent defaults it anyway as of 0.423.0 (feat(sdk): Default collapse=adjacentEvents on getProjectEvent sentry-api-schema#113).

Issues

• listIssues, getIssue, getIssueTagValues, getIssueExternalLinks, listIssueIntegrations, and getAutofixState now use their operations. listIssues still sends query= when it's empty, because Sentry applies is:unresolved only when the parameter is missing. A new test covers this. The two link lists share a small collectAllPages walker with listIssueLinkPages, which the Sentry App lists still use. The external-issues operation has no per_page, so that call relies on Sentry's default page size of 100, which is what it used to send.

Still on requestJSON/request()

• No @sentry/api operation: issue notes (createIssueComment, listIssueComments), getIssueActivity, getIssueUserReports, getEventCommitters.
• Writes: updateIssue, linkNativeExternalIssue, unlinkNativeExternalIssue, unlinkSentryAppExternalIssue, startAutofix. sdkClient() only forwards GETs. Letting it forward write bodies now would be replaced by the 6.1 transport anyway. The generated types also don't fit yet: updateOrganizationIssue marks every body field required, and deleteOrganizationIssueIntegration types externalIssue as a number.
• The attachment download (?download=1) and its redirect probe stay on request(), because they read binary data or the redirect URL rather than JSON.

The pnpm catalog moves @sentry/api from 0.420.0 to 0.423.0, the latest published version. #1712 makes the same bump, so either PR can land first. Regenerating the CLI's api-schema.json and idempotent-operations.json against 0.423.0 produced no changes.

via BYK.

--

View Junior Session in Sentry

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Oct 29, 2026 12:47am UTC