Supabase MCP (and other MCPs) setup error

Bug Reports
1

Title: Trouble Connecting MCP with Cursor on Windows 10

Environment

  • OS: Windows 10
  • Tools Tried: Supabase, GitHub integrations, MCP CLI

Problem
I’m trying to set up an MCP instance and connect to it using Cursor, but the connection never succeeds:

  • In both Supabase and GitHub-hosted setups, the MCP status shows a red “not connected” indicator.
  • Running the connection command manually in a terminal hangs for an extended period without any response.

What I’ve Tried

  1. Supabase CLI & Dashboard

    • Followed the official Supabase MCP guide step by step.
    • Deployed & started the MCP service; status remains “not connected.”

  2. GitHub Actions Deployment

    • Configured workflows according to common tutorials.
    • Workflow completes, but the MCP red dot persists.

  3. Manual CLI Connection

    • Ran mcp connect (or equivalent) in PowerShell/CMD.
    • No error output—just a long timeout.

  4. YouTube Tutorials

    • Followed multiple video walkthroughs showing quick, successful setups.
    • I’ve replicated each step exactly but still hit the same issue.

Logs & Screenshots

image
image745×351 15.7 KB

Questions

  • Has anyone encountered an MCP “not connected” status despite following the official docs?
  • Are there additional Windows 10-specific configurations or firewall rules I should check?
  • What debugging steps or log files could reveal why Cursor can’t establish the connection?

Any pointers would be greatly appreciated—thanks in advance!

1 Like
3

I have the same error, and I have already tried several things to solve it, but without success.