/ Verzeichnis / Playground / MCP Gateway & Registry
← Alle Server ↗ GitHub
● Community agentic-community 🔑 Eigener Schlüssel nötig

MCP Gateway & Registry

von 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.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

bereit

Installieren

Wählen Sie Ihren Client

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

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

~/.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 nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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}"
      }
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "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}"
      }
    }
  }
}

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

~/.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 nutzt ein Array von Serverobjekten statt einer Map.

~/.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"
        ]
      }
    }
  }
}

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

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

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

Anwendungsfälle

Praxisnahe Nutzung: MCP Gateway & Registry

Roll out MCP to a 200-person eng org

👤 Developers ⏱ ~15 min intermediate

Wann einsetzen: Different teams want different MCPs; you want central control without manual configs per dev.

Ablauf
  1. Deploy
    Stand up the gateway; wire it to your IdP.✓ Kopiert
    → Login works
  2. Register MCPs
    In the registry UI, add github, linear, sentry, internal-api MCPs with per-team scopes.✓ Kopiert
    → Servers visible
  3. Onboard
    Devs point Claude at https://mcp.corp/sse; gateway authorizes.✓ Kopiert
    → Devs use only what their team is allowed

Ergebnis: 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

Wann einsetzen: Security needs an answer to "who called what tool when".

Ablauf
  1. Enable audit sink
    Configure gateway to ship logs to your SIEM.✓ Kopiert
    → Logs flowing
  2. Query
    Search for tool calls touching production resources in last 24h.✓ Kopiert
    → Per-user trail returned

Ergebnis: Complete audit trail of MCP usage org-wide.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

mcp-gateway-registry + github-mcp

Register the official GitHub MCP behind the gateway with read-only org scope

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

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
gateway-passthrough (see docs) Tools are whatever the registered child servers expose 1 call

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
Bound by gateway host
Tokens pro Aufruf
Same as underlying tools
Kosten in €
Free OSS; your hosting
Tipp
Set per-principal quotas to prevent runaway agents

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: gateway-admin gateway-user
Credential-Speicherung: OIDC tokens; child-server credentials in vault
Datenabfluss: Where each child MCP egresses
Niemals gewähren: expose gateway publicly without OIDC

Fehlerbehebung

Häufige Fehler und Lösungen

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

Alternativen

MCP Gateway & Registry vs. andere

AlternativeWann stattdessenKompromiss
mcp-context-forgeYou want IBM's alternative gatewayDifferent ops model
Direct stdio configsSmall team, no central auth neededNo audit trail, no central scope

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen