Microsoft MCP Gateway

Name: Microsoft MCP Gateway MCP Server
Author: microsoft

왜 쓰나요

핵심 기능

Session-affinity routing for stateful MCP servers
Per-tenant isolation and quota
Centralized OAuth/OIDC at the gateway edge
Health probes + auto-restart of backend servers
Helm chart for Kubernetes deployment

라이브 데모

실제 사용 모습

microsoft-mcp-gateway.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

{
  "mcpServers": {
    "microsoft-mcp-gateway": {
      "command": "mcp-gateway",
      "args": [
        "serve"
      ]
    }
  }
}

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

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

{
  "mcpServers": {
    "microsoft-mcp-gateway": {
      "command": "mcp-gateway",
      "args": [
        "serve"
      ]
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "microsoft-mcp-gateway": {
      "command": "mcp-gateway",
      "args": [
        "serve"
      ]
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "microsoft-mcp-gateway": {
      "command": "mcp-gateway",
      "args": [
        "serve"
      ]
    }
  }
}

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

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "microsoft-mcp-gateway",
      "command": "mcp-gateway",
      "args": [
        "serve"
      ]
    }
  ]
}

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

~/.config/zed/settings.json

{
  "context_servers": {
    "microsoft-mcp-gateway": {
      "command": {
        "path": "mcp-gateway",
        "args": [
          "serve"
        ]
      }
    }
  }
}

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

claude mcp add microsoft-mcp-gateway -- mcp-gateway serve

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

사용 사례

실전 활용법: Microsoft MCP Gateway

Stand up an internal MCP catalog with one auth boundary

👤 Platform engineering teams ⏱ ~15 min intermediate

언제 쓸까: You have 10+ MCP servers and need centralized auth, quotas, and observability.

사전 조건

Server/skill installed and authenticated — See repo README

흐름

Deploy the gateway

Generate Helm values for mcp-gateway with our Entra OIDC issuer and three backend MCPs: github, jira, snowflake.✓ 복사됨

→ values.yaml + helm command
Register

Register each backend and assign it to the 'engineering' tenant with a 1000 req/hr quota.✓ 복사됨

→ Three backend ids + quota set

결과: One URL, one OIDC, many MCPs — properly governed.

함정

Session affinity is critical for stateful servers. If you switch to a stateless backend, also disable affinity to avoid hotspots. — Session affinity is critical for stateful servers. If you switch to a stateless backend, also disable affinity to avoid hotspots.

함께 쓰기: containers/kubernetes-mcp-server

조합

다른 MCP와 조합해 10배 효율

microsoft-mcp-gateway + containers/kubernetes-mcp-server

Pair with containers/kubernetes-mcp-server for complementary capabilities

Use this server together with containers/kubernetes-mcp-server to complete a multi-step task.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
list_backends	(none)	See registered MCP servers	1 API call
register_backend	name, image, env	Add a new MCP server behind the gateway	K8s scheduling
tenant_quota	tenant_id	Inspect or adjust per-tenant limits	1 API call

비용 및 제한

운영 비용

API 쿼터: See provider docs for rate limits
호출당 토큰: Varies by tool
금액: See repo README for pricing details
팁: Cache tool results and avoid repeated identical calls.

보안

권한, 시크릿, 파급범위

자격 증명 저장: Use environment variables; never commit secrets

데이터 외부 송신: Tool calls go to the provider's API as documented

문제 해결

자주 발생하는 오류와 해결

backend unhealthy

Gateway probes GET /healthz. Make sure your MCP server implements it or update healthCheck.path.

확인: kubectl get pods -n mcp

OIDC validation fails

Issuer URL must match the token's iss claim exactly, including trailing slash. Recheck Entra app config.

확인: Decode token at jwt.ms

대안