You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.