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.
Cursor review
Open this when the issue is making you decide whether a more code-first workflow is still the right long-term move.
Open this next →
Lovable reviews
Open this when the bug is making you reconsider whether a faster generated path would reduce the operational overhead.
Open this next →
Deploy hub
Open this when the fix is exposing a broader production handoff problem, not just one bug in the code.
Open this next →
Tool picker
Open this when repeated failures are pushing the decision back up to the stack level.
Open this next →
Firecrawl review
Open this when the app also needs live web data and the bigger stack question is no longer just about the coding tool.
Open this next →
Quick Fix Summary
| Most likely cause | Missing or malformed .cursor/mcp.json file, or Node.js version too old for the MCP server. |
| Fastest fix | Check .cursor/mcp.json |
| Use this page if | MCP 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
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"
]
}
}
}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
Cursor Not Understanding My Codebase
Cursor Agent Mode Stopping Mid-Task
Cursor Suggestions Arrive Too Late to Use
Cursor Changing Files I Didn't Ask It To
Cursor Says Context Limit Reached
Cursor Generating Pages Router Instead of App Router