How to manage 10+ MCP servers without config chaos
When to use: Your claude_desktop_config.json is a mile long and you don't know which servers are actually being used.
Prerequisites
- MCP Router installed — Download from github.com/mcp-router/mcp-router/releases
Flow
-
Import existing configOpen MCP Router → Import → point at Claude Desktop's config✓ Copied→ All servers listed with status
-
Create workspaces per projectCreate a workspace 'Client-Acme' and only enable GitHub + Sentry + Linear✓ Copied→ Minimal toolset for that project
-
Switch workspaces when switching projectsIn MCP Router, switch active workspace. Restart Claude.✓ Copied→ Claude sees only the enabled MCPs
Outcome: Clean tool surfaces per project — less context pollution for the model.
Pitfalls
- Claude caches tool list at session start — Always restart the client after switching workspace