Skip to content

Releases: supabase/mcp

mcp-utils: v0.7.0

Choose a tag to compare

@supabase-releaser supabase-releaser released this 20 Aug 12:15
c2826ee

0.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) (ead56f2)

mcp-server-supabase: v0.11.0

Choose a tag to compare

@supabase-releaser supabase-releaser released this 20 Aug 12:15
c2826ee

0.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, 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

  • add dual-era package serving entries (#358) (989eb4e)
  • migrate published packages to MCP SDK v2 (#327) (ead56f2)

mcp-server-postgrest: v0.2.0

Choose a tag to compare

@supabase-releaser supabase-releaser released this 20 Aug 12:15
c2826ee

0.2.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) (ead56f2)

mcp-utils: v0.6.0

Choose a tag to compare

@supabase-releaser supabase-releaser released this 10 Aug 18:38
302d2ad

0.6.0 (2026-08-10)

Features

mcp-server-supabase: v0.10.0

Choose a tag to compare

@supabase-releaser supabase-releaser released this 10 Aug 18:38
302d2ad

0.10.0 (2026-08-10)

⚠ BREAKING CHANGES

  • add query_logs tool for custom log queries (#333)

Features

  • add --content-api-url flag and SUPABASE_CONTENT_API_URL env var (#343) (6fcaaa3)
  • add query_logs tool for custom log queries (#333) (798806b)
  • hide tools from tools/list (#334) (d80471a)

Bug Fixes

  • hide read-only mode (#349) (5cda067)
  • pg-meta: pair composite FK columns positionally to avoid cartesi… (#317) (10af00b)
  • select query_logs dialect via logsDialect (#357) (80ff453)

mcp-server-supabase: v0.9.0

Choose a tag to compare

@supabase-releaser supabase-releaser released this 17 Jul 09:07
4690aa9

0.9.0 (2026-07-16)

Features

  • support edge function runtime logs in get_logs (#326) (b9675aa)

mcp-server-supabase: v0.8.3

Choose a tag to compare

@supabase-releaser supabase-releaser released this 15 Jul 11:22
b8dfc3f

0.8.3 (2026-07-15)

Bug Fixes

  • actionable error for wrong-org permission failures on database tools (#329) (add45f5)

mcp-utils: v0.5.1

Choose a tag to compare

@mattrossman mattrossman released this 08 Jun 16:04
b9b1177

0.5.1 (2026-06-05)

Bug Fixes

  • update repo URLs after supabase/mcp transfer (#295) (71e48cc)

mcp-server-supabase: v0.8.2

Choose a tag to compare

@mattrossman mattrossman released this 08 Jun 16:05
b9b1177

0.8.2 (2026-06-05)

Bug Fixes

  • test: resolve edge function test typo and invalid branch array access (#279) (da182d6)
  • update repo URLs after supabase/mcp transfer (#295) (71e48cc)

mcp-server-postgrest: v0.1.1

Choose a tag to compare

@mattrossman mattrossman released this 08 Jun 16:05
b9b1177

0.1.1 (2026-06-05)

Bug Fixes

  • update repo URLs after supabase/mcp transfer (#295) (71e48cc)