Describe the Bug
I posted this bug April 12th… no responses, was automatically closed. I’m still having this issue and surprised it’s not bothering anyone else:
I recently tried renaming to production_supabase and development_supabase, but that doesn’t help either.
I have MCP setup for supabase dev and supabase production… If i have both enabled, it will always check the first one in the order and ignore the second. it will also call the same one twice for comparisons…
to test:
supabase_dev
supabase_prod (listed second)
Ask it to check a table for a missing column in both local and remote…
it will say the column exists in both, even when it only exists in dev
if you reverse the order in the MCP file and put production first, it will say its missing in both
As a workaround i just disable one of them but it’s pretty annoying.
MacOs 15.3.2
Doesn’t prevent me from using Cursor
Steps to Reproduce
create the same mcp for 2 different environments, and ask it to compare, it will only look at one and tell you they are the same
Expected Behavior
it should look at each one in the context of the chat
“check the dev db if this table exists…” should use supabase_dev mcp not supabase_prod
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.3
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:35:49.230Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Does this stop you from using Cursor
No - Cursor works, but with this issue