supabase / mcp / 32367864500

97%

push

github

chore: release main (#370)

:robot: I have created a release *beep* *boop*
---


<details><summary>mcp-utils: 0.7.0</summary>

##
[0.7.0](https://github.com/supabase/mcp/compare/mcp-utils-v0.6.0...mcp-utils-v0.7.0)
(2026-08-20)


### ⚠ BREAKING CHANGES

* the peer dependency is now `@modelcontextprotocol/server` instead of
`@modelcontextprotocol/sdk`, so consumers must install the new package.
`@supabase/mcp-utils` also drops the exported types `ExtractRequest`,
`ExtractNotification`, `ExtractResult` and `ExpandRecursively`, and
`createMcpServer` returns a bare `Server` rather than `Server<Request,
Notification, Result>`, because v2's `Server` class takes no type
parameters. Because that returned value is now a v2 `Server`, a consumer
who registered extra handlers on it must rewrite
`server.setRequestHandler(SomeRequestSchema, ...)` as
`server.setRequestHandler('some/method', ...)`; the v1 Zod-schema
overload no longer exists. `InitData.clientCapabilities` now follows
v2's `ClientCapabilities`, which is narrower than v1's and not
assignable from it. Finally, a `tools/call` request whose `params` are
malformed, meaning no `name` key or a non-string `name`, now returns
JSON-RPC `-32602` with the message prefix `Invalid tools/call request: `
where v1 returned `-32603` with a bare stringified ZodError.

### Features

* migrate published packages to MCP SDK v2
([#327](https://github.com/supabase/mcp/issues/327))
([ead56f2](https://github.com/supabase/mcp/commit/ead56f228))
</details>

<details><summary>mcp-server-supabase: 0.11.0</summary>

##
[0.11.0](https://github.com/supabase/mcp/compare/mcp-server-supabase-v0.10.0...mcp-server-supabase-v0.11.0)
(2026-08-20)


### ⚠ BREAKING CHANGES

* the peer dependency is now `@modelcontextprotocol/server` instead of
`@modelcontextprotocol/sdk`, so consumers must install the new package.
`@supabase/mcp-utils` also drops the exported types `ExtractRequest`,
`ExtractNotification`, `Extra... (continued)

350 of 384 branches covered (91.15%)

Branch coverage included in aggregate %.

2951 of 3036 relevant lines covered (97.2%)

50.92 hits per line