mcp-router MCP — Cas d'usage, Installer & Démo en direct

Name: mcp-router MCP Server
Author: mcp-router

Pourquoi l'utiliser

Fonctionnalités clés

Toggle individual tools on/off per workspace/project
Centralized request logging and analytics
Works with Claude Desktop, Cursor, Cline, Windsurf
100% local — credentials never leave the device

Démo en direct

Aperçu en pratique

router.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "router": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-router"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "router": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-router"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "router": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-router"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "router": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-router"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "router",
      "command": "npx",
      "args": [
        "-y",
        "mcp-router"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "router": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-router"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add router -- npx -y mcp-router

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcp-router

How to manage 10+ MCP servers without config chaos

👤 Power users with MCPs piling up ⏱ ~20 min beginner

Quand l'utiliser : Your claude_desktop_config.json is a mile long and you don't know which servers are actually being used.

Prérequis

MCP Router installed — Download from github.com/mcp-router/mcp-router/releases

Déroulement

Import existing config

Open MCP Router → Import → point at Claude Desktop's config✓ Copié

→ All servers listed with status
Create workspaces per project

Create a workspace 'Client-Acme' and only enable GitHub + Sentry + Linear✓ Copié

→ Minimal toolset for that project
Switch workspaces when switching projects

In MCP Router, switch active workspace. Restart Claude.✓ Copié

→ Claude sees only the enabled MCPs

Résultat : Clean tool surfaces per project — less context pollution for the model.

Pièges

Claude caches tool list at session start — Always restart the client after switching workspace

Audit which MCP tools your agents actually use

👤 Anyone optimizing their setup ⏱ ~15 min beginner

Quand l'utiliser : You wonder if half your MCPs are ever actually called — cut the dead weight.

Déroulement

Let it log for a week

Enable request logging in MCP Router → use Claude normally for 7 days✓ Copié

→ Log accumulates real usage
Review analytics

Open MCP Router → Analytics. Which servers were called <5 times? Sort by call count.✓ Copié

→ Clear top / tail split
Disable or uninstall the tail

For servers in the bottom 25%, disable them or remove entirely✓ Copié

→ Leaner setup

Résultat : Data-driven MCP pruning — faster startup, less tool-choice confusion.

Gate dangerous MCP tools behind explicit enable

👤 Security-conscious users ⏱ ~10 min intermediate

Quand l'utiliser : You have a GitHub MCP with write scopes but only want it on when you're actively fixing code.

Déroulement

Disable write tools by default

In MCP Router, disable create_issue, create_pull_request, delete_repo for the GitHub server. Keep reads on.✓ Copié

→ Only read tools advertised to Claude
Enable briefly when needed

About to file a PR — enable create_pull_request, run the flow, disable again✓ Copié

→ Short enabled windows; audit log captures the calls

Résultat : Default-deny for destructive operations.

Combiner avec : mcptools

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

router + mcptools

MCP Router for day-to-day, mcptools (guard) for scripted CI gating

Use MCP Router to disable github writes on my dev machine; in CI use mcp guard policy file.✓ Copié

router + copilot

Discover new MCPs with copilot-mcp, manage them centrally with MCP Router

Install 3 new MCPs via copilot-mcp, then organize them into the 'Research' workspace in MCP Router.✓ Copié

Coût et limites

Coût d'exécution

Quota d'API: N/A — desktop app
Tokens par appel: N/A
Monétaire: Free, open source
Astuce: Use workspaces aggressively — each workspace keeps only the tools you need, reducing per-session token overhead

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Credentials stored locally in MCP Router's settings; never transmitted

Sortie de données : None from the router itself; downstream MCPs go wherever they normally do

Dépannage

Erreurs courantes et correctifs

Claude still sees disabled tools

Claude caches at session start — fully quit and relaunch (not just reload)

Vérifier : Ask Claude to list its available tools

Import fails on large configs

Malformed JSON is the usual culprit. Validate config with jq . claude_desktop_config.json first

Server won't start from router

The router uses the same command as Claude — run it in a terminal manually to see the real error

Alternatives

mcp-router vs autres

Alternative	Quand l'utiliser	Compromis
copilot-mcp (VSCode)	You live in VSCode and prefer extensions	VSCode-bound
Manual config editing	You have 1-3 MCPs total	No logging, no workspace switching

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills