freemcplab / 目錄 / 演練場 / MCP Gateway & Registry

● 社群 agentic-community 🔑 需要你的金鑰

MCP Gateway & Registry

Name: MCP Gateway & Registry MCP Server
Author: agentic-community

作者 agentic-community · agentic-community/mcp-gateway-registry

One HTTP endpoint that fronts every internal MCP server — central auth, per-team namespaces, audit log, and a web UI for discovery.

Instead of giving every developer a list of stdio configs, run this gateway once: it registers child MCP servers, brokers connections, enforces auth, and exposes a discovery UI. Developers point Claude at one URL.

▶ 觀看演示 📦 安裝 💡 使用場景

為什麼要用

核心特性

Single HTTP/SSE endpoint fronts many MCPs
Per-user / per-team auth (OIDC, tokens)
Registry UI listing available servers
Centralized audit log of every tool call
Rate limiting and quotas per principal
Hot-reload server config without client restart

即時演示

實際使用效果

就緒

安裝

選擇你的客戶端

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

{
  "mcpServers": {
    "mcp-gateway-registry": {
      "command": "docker",
      "args": [
        "run",
        "-p",
        "8080:8080",
        "-e",
        "GATEWAY_TOKEN",
        "ghcr.io/agentic-community/mcp-gateway-registry:latest"
      ],
      "env": {
        "GATEWAY_TOKEN": "${GATEWAY_TOKEN}"
      }
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

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

{
  "mcpServers": {
    "mcp-gateway-registry": {
      "command": "docker",
      "args": [
        "run",
        "-p",
        "8080:8080",
        "-e",
        "GATEWAY_TOKEN",
        "ghcr.io/agentic-community/mcp-gateway-registry:latest"
      ],
      "env": {
        "GATEWAY_TOKEN": "${GATEWAY_TOKEN}"
      }
    }
  }
}

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "mcp-gateway-registry": {
      "command": "docker",
      "args": [
        "run",
        "-p",
        "8080:8080",
        "-e",
        "GATEWAY_TOKEN",
        "ghcr.io/agentic-community/mcp-gateway-registry:latest"
      ],
      "env": {
        "GATEWAY_TOKEN": "${GATEWAY_TOKEN}"
      }
    }
  }
}

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-gateway-registry": {
      "command": "docker",
      "args": [
        "run",
        "-p",
        "8080:8080",
        "-e",
        "GATEWAY_TOKEN",
        "ghcr.io/agentic-community/mcp-gateway-registry:latest"
      ],
      "env": {
        "GATEWAY_TOKEN": "${GATEWAY_TOKEN}"
      }
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "mcp-gateway-registry",
      "command": "docker",
      "args": [
        "run",
        "-p",
        "8080:8080",
        "-e",
        "GATEWAY_TOKEN",
        "ghcr.io/agentic-community/mcp-gateway-registry:latest"
      ]
    }
  ]
}

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

{
  "context_servers": {
    "mcp-gateway-registry": {
      "command": {
        "path": "docker",
        "args": [
          "run",
          "-p",
          "8080:8080",
          "-e",
          "GATEWAY_TOKEN",
          "ghcr.io/agentic-community/mcp-gateway-registry:latest"
        ]
      }
    }
  }
}

加入 context_servers。Zed 儲存後熱重載。

claude mcp add mcp-gateway-registry -- docker run -p 8080:8080 -e GATEWAY_TOKEN ghcr.io/agentic-community/mcp-gateway-registry:latest

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： MCP Gateway & Registry

Roll out MCP to a 200-person eng org

👤 Developers ⏱ ~15 min intermediate

何時使用： Different teams want different MCPs; you want central control without manual configs per dev.

步驟

Deploy

Stand up the gateway; wire it to your IdP.✓ 已複製

→ Login works
Register MCPs

In the registry UI, add github, linear, sentry, internal-api MCPs with per-team scopes.✓ 已複製

→ Servers visible
Onboard

Devs point Claude at https://mcp.corp/sse; gateway authorizes.✓ 已複製

→ Devs use only what their team is allowed

結果： Centralized rollout with per-team scopes and one config to ship to clients.

Audit every MCP tool call across the org

👤 Developers ⏱ ~15 min intermediate

何時使用： Security needs an answer to "who called what tool when".

步驟

Enable audit sink

Configure gateway to ship logs to your SIEM.✓ 已複製

→ Logs flowing
Query

Search for tool calls touching production resources in last 24h.✓ 已複製

→ Per-user trail returned

結果： Complete audit trail of MCP usage org-wide.

組合

與其他 MCP 搭配，撬動十倍槓桿

mcp-gateway-registry + github-mcp

Combine mcp-gateway-registry with github-mcp: Register the official GitHub MCP behind the gateway with read-only org scope✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫	成本
gateway-passthrough	(see docs)	Tools are whatever the registered child servers expose	1 call

成本與限制

運行它的成本

API 配額: Bound by gateway host
每次呼叫 Token 數: Same as underlying tools
費用: Free OSS; your hosting
提示: Set per-principal quotas to prevent runaway agents

安全

權限、密鑰、影響範圍

最小權限： gateway-admin gateway-user

憑證儲存： OIDC tokens; child-server credentials in vault

資料出站： Where each child MCP egresses

切勿授予： expose gateway publicly without OIDC

故障排查

常見錯誤與修復

Tool list empty

Check the principal has scope for at least one registered server

Slow first call

Gateway lazy-starts child servers; pre-warm hot ones

替代方案