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와 조합해 10배 효율

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
호출당 토큰: 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

대안