Cursor·Fixdeployintermediate

Cursor MCP Server Not Connecting

Quick Answer

How do I fix Cursor MCP Server Not Connecting?

Missing or malformed .cursor/mcp.json file, or Node.js version too old for the MCP server. Start with "Check .cursor/mcp.json" before making broader code changes.

Fix signals

What this answers
Why cursor mcp server not connecting happens and what to change first.
Fastest move
Check .cursor/mcp.json
Use this page if
MCP tools not appearing in Cursor

If this keeps happening

Open the next decision, not just the patch

Use these when the current fix is helpful, but the real answer is a better tool choice, a cleaner workflow layer, or a more trustworthy launch path.

Quick Fix Summary

Most likely causeMissing or malformed .cursor/mcp.json file, or Node.js version too old for the MCP server.
Fastest fixCheck .cursor/mcp.json
Use this page ifMCP tools not appearing in Cursor

You're in the right place if...

  • !MCP tools not appearing in Cursor
  • !Connection error in MCP settings
  • !Timeout when trying to use MCP

Why this happens

Missing or malformed .cursor/mcp.json file, or Node.js version too old for the MCP server.

Fix

1

Check .cursor/mcp.json

Verify the file exists and is valid JSON:

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase@latest",
        "--supabase-url", "YOUR_URL",
        "--supabase-key", "YOUR_KEY"
      ]
    }
  }
}
2

Refresh MCP

Cursor Settings → MCP → click the refresh button. If still failing, check that Node.js 18+ is installed.

Prevent this next time

Test MCP connections immediately after setup. Don't wait until you need them.

Frequently Asked Questions

Model Context Protocol. It lets Cursor connect to external tools like Supabase, GitHub, or databases directly.

Not required, but very useful. MCP lets Cursor read your actual database schema instead of guessing.

Related fixes