mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
Pedro RodriguesandClaude Sonnet 5
e5f2b29625
## Summary - Removes the `USE_REMOTE_MCP` env-var gate from the dashboard assistant: `getMcpTools` now always connects to the remote MCP server (the rollout from #47479 has been stable ~2 months and is enabled in prod). - Drops the var from `apps/studio/turbo.jsonc` and deletes the now-obsolete transport-selection tests. - The legacy in-process client (`createInProcessSupabaseMCPClient`) stays, re-scoped to the hermetic eval harness (`mock-tools.ts`, `evals/preflight.ts`); removing it is tracked by AI-897. ## Verification - `pnpm exec tsc --noEmit` in apps/studio: no errors in any changed file (one pre-existing unrelated error in `packages/ui-patterns/.../InstructionBlocks.tsx`). - `mcp-tools.test.ts` (7), `mock-tools.test.ts` (15), `tools/index.test.ts` (6), `supabase-mcp.test.ts` (11) all pass. ## Risk Low. Remote failure already degrades to non-MCP tools in `getTools`; rollback = revert this PR (or re-add the gate). ## Follow-up After this lands in prod, `USE_REMOTE_MCP` can be removed from the Vercel env vars — nothing in the repo reads it anymore. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Improvements** * AI tools now consistently use the remote service when retrieving available tools. * If the remote service is unavailable, times out, or cannot authenticate, the assistant continues operating with the tools that remain available. * Evaluation and development behavior now more closely reflects the remote service experience. * **Maintenance** * Updated supporting documentation and automated coverage to reflect the streamlined tool connection behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>