supabase / mcp / 32367232457

97%

push

github

feat: add dual-era package serving entries (#358)

> **This is a stacked PR. Its parent is #327, please review that one
first.**
>
> The diff here is only this branch's own commits. The base is
`raulb/spike-mcp-v2` rather than `main` on purpose, because #327 is
still in review; once it lands, this retargets to `main` and the diff
against `main` shrinks accordingly.
>
> The `test` check runs on this page and passes at `851f01e`. An earlier
version of this description said it would be absent; that note is out of
date. The test output under Verification came from a local run that
predates the check.
>
> At merge time: retarget to `main`, let `tests.yml` run green there,
then merge.

## What kind of change does this PR introduce?

The CLI serves both protocol eras from one tool definition, and the
package exports one modern HTTP handler for the hosted `/mcp` endpoint
to mount.

PR 2 of 3 for
[AI-1044](https://linear.app/supabase/issue/AI-1044/migrate-mcp-server-supabase-to-mcp-sdk-v2)
([plan](https://linear.app/supabase/document/mcp-sdk-v2-migration-plan-d19bb064d673)).

## What is the current behavior?

`src/transports/stdio.ts` connects a raw `StdioServerTransport`, so only
2025-era clients are served, and there's no HTTP entry for hosted to
consume.

## What is the new behavior?

`serveStdio` owns the transport and picks the era per connection.
`createSupabaseMcpHandler` wraps the SDK's `createMcpHandler` with
`legacy: 'reject'`, so hosted keeps authentication, ABAC, era dispatch,
and logging.

`tools/list` is unchanged, so the frozen ChatGPT contract is unaffected.
`mcp-server-postgrest` keeps its single-era entry, and nothing here adds
Elicitation machinery, tool policies, or telemetry.

## Verification

- `mcp-server-supabase` unit + integration: **222 passed**. Both eras
run against the real built `dist/transports/stdio.js`, spawned as a
child process.
- `mcp-utils`: **12 passed**. `pnpm build` and `pnpm format:check`
clean.
- `pnpm test:packed-pla... (continued)

350 of 384 branches covered (91.15%)

Branch coverage included in aggregate %.

6 of 6 new or added lines in 1 file covered. (100.0%)

2951 of 3036 relevant lines covered (97.2%)

50.92 hits per line