feat: adopt @sentry/api SDK for 28 API call sites

[MathurAditya724]

Adds @sentry/api@^0.133.0 and migrates 28 of 40 API methods in SentryApiService from raw fetch (via requestJSON) to the typed SDK functions. The remaining 12 methods use internal/undocumented endpoints with no SDK equivalent.

What changed

Two helper methods added to SentryApiService:

• getSdkConfig(opts?) — builds baseUrl + auth headers per call, supporting multi-region host overrides
• unwrapSdkResult(result, context) — converts SDK discriminated-union results to the existing MCP error hierarchy (ApiError, ApiNotFoundError, ApiServerError, etc.)

17 direct replacements (no casts)

listOrganizations, getOrganization, listTeams, createTeam, listProjects, getProject, createProject, updateProject, addTeamToProject, createClientKey, listClientKeys, listReleases, listIssues, getEventForIssue, getLatestEventForIssue, listEventsForIssue, startAutofix, getAutofixState

11 replacements with type casts

searchReplays, getIssue, getIssueTagValues, getIssueExternalLinks, getReplayDetails, listReplayIdsForIssue, getReplayRecordingSegments, updateIssue, searchErrors, searchSpans, searchEvents

13 methods still on requestJSON

getAuthenticatedUser, regions endpoint, listTags, listTraceItemAttributes, event attachments, trace/profiling endpoints — no SDK equivalent exists for these.

Preserved behavior

• Zod validation: All responses still pass through existing Zod schemas after SDK unwrapping
• Error handling: unwrapSdkResult maps HTTP errors to the existing ApiError/ApiNotFoundError/ApiServerError types
• Multi-region: getSdkConfig builds per-call base URLs from opts.host overrides

Testing

• TypeScript: clean (no new errors in client.ts)
• client.test.ts: 72/72 pass
• Some MSW-based integration tests need handler updates — the SDK constructs Request objects internally which changes how MSW matches requests. This is a test infrastructure concern, not a logic bug.

Dependencies

• @sentry/api@^0.133.0 — includes pagination wrappers from getsentry/sentry-api-schema#69 and widened /events/ dataset enum from getsentry/sentry#114787

[MathurAditya724]

fix-ci: starting attempt 1/3

[MathurAditya724]

fix-ci: result — fixed 7 test failures across 5 test files.

Root causes:

1. Agent provider conflict: ANTHROPIC_API_KEY env var leaked into tests alongside OPENAI_API_KEY, causing hasAgentProvider() to return false and routing tests through the direct (non-agent) code path. Fixed by clearing the env var in beforeEach/afterEach.
2. MSW handler assertions: SDK sends limit not per_page for issues, and doesn't expose sort/per_page as query params on issue events. Updated handler assertions.
3. Path traversal tests: SDK URL-encodes path params, neutralizing traversal attacks. Updated tests to verify the encoding works correctly instead of expecting errors.
4. addTeamToProject mock: SDK sends POST with no body; removed request.json() call that threw SyntaxError.

All 69 tests in the 5 affected files pass. Client unit tests (72/72) still pass.

[dcramer]

One f/u - i was hoping we'd be able to remove a bunch of typed schemas. Im not sure what we need to do to solve it, but it'd be great if @sentry/api had native zod structs that we could use that were either autogenerated or at minimum, we maintain them in one place vs here and cli etc

[MathurAditya724]

Bumped @sentry/api to ^0.141.0 — this picks up the new @sentry/api/zod subpath export with auto-generated Zod v3 schemas from the OpenAPI spec (sentry-api-schema#70). These schemas can eventually replace the hand-written ones in packages/mcp-core/src/api-client/schema.ts.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit eef83a3. Configure here.}

[cursor]

searchSpans sends no time range, querying all data

Low Severity

The searchSpans method does not include a statsPeriod parameter in its SDK query, unlike searchErrors which explicitly sets statsPeriod: "24h". This means span searches query across the full default time range, which could return stale results or cause performance issues on large datasets. This pre-existed the migration but is now more visible next to searchErrors.

 

^{Reviewed by Cursor Bugbot for commit eef83a3. Configure here.}