chore(platform-lite): bump Supabase MCP to 0.12.0

[barryroodt]

Summary

• Bump the platform-lite Supabase MCP dependency to 0.12.0.
• Refresh the pnpm lockfile, including transitive mcp-utils 0.8.0.
• Keep the platform-lite integration unchanged after reviewing the 0.12.0 cost-confirmation behavior.

Changelog review

platform-lite uses the MCP platform API with an access token and API URL. It does not enable cost confirmation or depend on the legacy cost tools, so 0.12.0 needs no integration change.

Testing

• pnpm install --frozen-lockfile
• pnpm --filter @supabase-evals/platform-lite typecheck
• pnpm exec biome check packages/platform-lite
• pnpm --filter @supabase-evals/platform-lite exec vitest run test/mcp-platform.test.ts test/clickhouse-logs.test.ts

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
evals	Ignored	Preview	Sep 7, 2026 1:53pm UTC

[Rodriguespn]

Thanks for take care of this Barry. AFAIK, we would still need to bump the MCP server version in here right?

evals/packages/core/src/index.ts

Line 1256 in 1d859a7

export const MCP_SERVER_VERSION = '0.11.0';

This is the MCP Server version we're using when running the evals.

npx @supabase/mcp-server-supabase@0.11.0 --access-token <token> --features docs,account,database,development,debugging,functions [--api-url <url>]

The npm package used in packages/platform-lite/package.json is used only on the platform-lite tests

[barryroodt]

Good catch @Rodriguespn. I bumped the eval launcher default to 0.12.0 in efd8bc8.

[Rodriguespn]

Approved 🚢
Platform-lite bumps to ^0.12.0 and the harness runtime pin (MCP_SERVER_VERSION) now tracks 0.12.0; lockfile clean, typecheck and all core/platform-lite tests pass, and no integration change is needed (cost confirmation is opt-in and unused).