mcp-router MCP — Anwendungsfälle, Installieren & Live-Demo

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

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

router.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren 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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: mcp-router

How to manage 10+ MCP servers without config chaos

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

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

Voraussetzungen

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

Ablauf

Import existing config

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

→ All servers listed with status
Create workspaces per project

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

→ Minimal toolset for that project
Switch workspaces when switching projects

In MCP Router, switch active workspace. Restart Claude.✓ Kopiert

→ Claude sees only the enabled MCPs

Ergebnis: Clean tool surfaces per project — less context pollution for the model.

Fallstricke

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

Wann einsetzen: You wonder if half your MCPs are ever actually called — cut the dead weight.

Ablauf

Let it log for a week

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

→ Log accumulates real usage
Review analytics

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

→ Clear top / tail split
Disable or uninstall the tail

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

→ Leaner setup

Ergebnis: Data-driven MCP pruning — faster startup, less tool-choice confusion.

Gate dangerous MCP tools behind explicit enable

👤 Security-conscious users ⏱ ~10 min intermediate

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

Ablauf

Disable write tools by default

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

→ Only read tools advertised to Claude
Enable briefly when needed

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

→ Short enabled windows; audit log captures the calls

Ergebnis: Default-deny for destructive operations.

Kombinieren mit: mcptools

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: N/A — desktop app
Tokens pro Aufruf: N/A
Kosten in €: Free, open source
Tipp: Use workspaces aggressively — each workspace keeps only the tools you need, reducing per-session token overhead

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Credentials stored locally in MCP Router's settings; never transmitted

Datenabfluss: None from the router itself; downstream MCPs go wherever they normally do

Fehlerbehebung

Häufige Fehler und Lösungen

Claude still sees disabled tools

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

Prüfen: 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

Alternativen

mcp-router vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen