mcp-router MCP — 사용 사례, 설치 & 라이브 데모

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

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

router.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/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
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

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

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

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

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

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

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

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

context_servers에 추가. 저장 시 Zed가 핫 리로드.

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

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: mcp-router

How to manage 10+ MCP servers without config chaos

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

언제 쓸까: Your claude_desktop_config.json is a mile long and you don't know which servers are actually being used.

사전 조건

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

흐름

Import existing config

Open MCP Router → Import → point at Claude Desktop's config✓ 복사됨

→ All servers listed with status
Create workspaces per project

Create a workspace 'Client-Acme' and only enable GitHub + Sentry + Linear✓ 복사됨

→ Minimal toolset for that project
Switch workspaces when switching projects

In MCP Router, switch active workspace. Restart Claude.✓ 복사됨

→ Claude sees only the enabled MCPs

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

함정

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

언제 쓸까: You wonder if half your MCPs are ever actually called — cut the dead weight.

흐름

Let it log for a week

Enable request logging in MCP Router → use Claude normally for 7 days✓ 복사됨

→ Log accumulates real usage
Review analytics

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

→ Clear top / tail split
Disable or uninstall the tail

For servers in the bottom 25%, disable them or remove entirely✓ 복사됨

→ Leaner setup

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

Gate dangerous MCP tools behind explicit enable

👤 Security-conscious users ⏱ ~10 min intermediate

언제 쓸까: You have a GitHub MCP with write scopes but only want it on when you're actively fixing code.

흐름

Disable write tools by default

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

→ Only read tools advertised to Claude
Enable briefly when needed

About to file a PR — enable create_pull_request, run the flow, disable again✓ 복사됨

→ Short enabled windows; audit log captures the calls

결과: Default-deny for destructive operations.

함께 쓰기: mcptools

조합

다른 MCP와 조합해 10배 효율

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.✓ 복사됨

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.✓ 복사됨

비용 및 제한

운영 비용

API 쿼터: N/A — desktop app
호출당 토큰: N/A
금액: Free, open source
팁: Use workspaces aggressively — each workspace keeps only the tools you need, reducing per-session token overhead

보안

권한, 시크릿, 파급범위

자격 증명 저장: Credentials stored locally in MCP Router's settings; never transmitted

데이터 외부 송신: None from the router itself; downstream MCPs go wherever they normally do

문제 해결

자주 발생하는 오류와 해결

Claude still sees disabled tools

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

확인: 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

대안

mcp-router 다른 것과 비교

대안	언제 쓰나	단점/장점
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

mcp-router