mcp-server-supabase: v0.13.0

0.13.0 (2026-09-17)

⚠ BREAKING CHANGES

• mcp: confirm destructive SQL via elicitation and rename costConfirmation option (#408)

Features

• add --http local HTTP entry to mcp-server-supabase (#401) (ff063b4)
• management: add v2 api client (#419) (02ca542)
• mcp: confirm destructive SQL via elicitation and rename costConfirmation option (#408) (c9c4e3f)
• support skip_elicitations in the local HTTP server (#434) (9442e82)
• URL-mode secret collection for create_edge_function_secret (#412) (fb88629)

Bug Fixes

• discourage host-filesystem access in raw-SQL tool descriptions (#410) (641ed1e)

mcp-utils: v0.8.0

0.8.0 (2026-09-04)

Features

• mcp: add project cost confirmation elicitation (#391) (fb50882)
• mcp: hide legacy cost tools from form-capable clients (#411) (2f04461)

mcp-server-supabase: v0.12.0

0.12.0 (2026-09-04)

Features

• group lints in get_advisors response (#390) (48d593a)
• mcp: add branch cost confirmation elicitation (#394) (867a160)
• mcp: add project cost confirmation elicitation (#391) (fb50882)
• mcp: hide legacy cost tools from form-capable clients (#411) (2f04461)

Bug Fixes

• ensure correct escaping in advisor (#407) (a6cf4a0)
• make server instructions intent-based instead of naming tools (#372) (fc54ea2)

mcp-utils: v0.7.0

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

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

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

0.6.0 (2026-08-10)

Features

• hide tools from tools/list (#334) (d80471a)

mcp-server-supabase: v0.10.0

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

0.9.0 (2026-07-16)

Features

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

mcp-server-supabase: v0.8.3

0.8.3 (2026-07-15)

Bug Fixes

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