📝 Fix: How to eliminate duplicate MCP server instances showing in C...

Date: 2026-02-07
Time: 21:27:49 UTC
Session: gspace1-99.6
Agent: testing
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How to eliminate duplicate MCP server instances showing in Cursor?

Task: Fix duplicate MCP server instances in Cursor

🎯 Decision Made

Chosen:

Moved mcp-gograb-ai from global ~/.cursor/mcp.json to per-project .cursor/mcp.json in each workspace (gspace1 and editor2). Global config now only contains Playwright.

Options Considered:

• No alternatives documented

💭 Reasoning

Cursor loads MCP servers from both the global config (~/.cursor/mcp.json) and per-project config (.cursor/mcp.json). When both defined mcp-gograb-ai, Cursor displayed two instances — one from each source. By removing it from global and defining it only at the project level, each workspace gets exactly one MCP instance pointing to its own start-server.sh script. This also complements the dynamic workspace detection fix from earlier: each workspace's .cursor/mcp.json points to its own start-server.sh, and the script detects $PWD to resolve the correct WORKSPACE_ROOT.

📁 Files Involved

• /Users/fguijarro/.cursor/mcp.json
• /Users/fguijarro/developer/repos-gspace/gspace1/.cursor/mcp.json
• /Users/fguijarro/developer/repos/editor2/.cursor/mcp.json

🔗 Related

• Decision ID: dev_1770499669747_5ertiib
• Session: 99
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation