MCP 게이트웨이는 모델 컨텍스트 프로토콜(MCP) 서버용 역프록시 및 관리 계층으로, Kubernetes 환경에서 MCP 서버의 확장 가능하고 상태 없는 요청 라우팅, 권한 부여 및 수명 주기 관리를 가능하게 합니다.

변경사항: 이 버전은 MCP 2026-07-28 클라이언트와 어댑터를 요구합니다. 레거시 초기화, 전송 세션, 프로토콜 다운그레이드를 제공하지 않습니다. 클라이언트 요구사항, 요청 예시, 배포 설정 및 롤백 고려사항에 대해서는 마이그레이션 가이드를 참조하세요.

목차

• 개요
• 핵심 개념
• 건축
• 특징
• 시작 – 로컬 배포
• 시작 – 1클릭으로 Azure로 배포

개요

이 프로젝트는 다음을 제공합니다:

• 각 MCP 요청을 독립적으로 준비된 서버 인스턴스로 라우팅하는 데이터 게이트웨이.
• MCP 서버 수명주기(배포, 업데이트, 삭제)를 관리하는 제어 플레인.
• 텔레메트리, 접근 제어 및 관측성을 포함한 엔터프라이즈 통합 포인트.

주요 개념

• MCP 서버: 모델 컨텍스트 프로토콜을 구현하는 서버로, 일반적으로 스트리밍 가능한 HTTP 엔드포인트입니다.

MCP Gateway

MCP Gateway is a reverse proxy and management layer for Model Context Protocol (MCP) servers, enabling scalable, stateless request routing, authorization and lifecycle management of MCP servers in Kubernetes environments.

Breaking change: this version requires MCP 2026-07-28 clients and adapters. It does not provide legacy initialization, transport sessions, or protocol downgrade. See the migration guide for client requirements, request examples, deployment settings, and rollback considerations.

Table of Contents

• Overview
• Key Concepts
• Architecture
• Features
• Getting Started – Local Deployment
• Getting Started – 1-Click Deploy to Azure

Overview

This project provides:

• A data gateway for independently routing each MCP request to a ready server instance.
• A control plane for managing the MCP server lifecycle (deploy, update, delete).
• Enterprise-ready integration points including telemetry, access control and observability.

Key Concepts

• MCP Server: A server implementing the Model Context Protocol, which typically a streamable HTTP endpoint.
• Adapters: Logical resources representing MCP servers in the gateway, managed under the /adapters scope. Designed to coexist with other resource types (e.g., /agents) in a unified AI development platform.
• Tools: Registered resources with MCP tool definitions that can be dynamically routed via the tool gateway router. Each tool includes metadata about its execution endpoint and input schema.
• Tool Gateway Router: An MCP server that directs tool execution requests to registered tool servers based on tool definitions. Multiple router instances can handle requests without transport-session affinity.
• Stateless MCP Routing: Each request carries its protocol metadata and is independently authorized. Legacy session headers and the gateway’s session_id query alias do not determine routing.
• Agents & Sessions (Preview): Optional, opt-in resources for running LLM-driven agents on top of registered MCP tools. Agents are metadata (system prompt + model + allowed tool list); Sessions are individual runs that stream events over Server-Sent Events. Disabled unless FoundrySettings:Endpoint is configured.

Architecture

flowchart LR
    subgraph Clients[" "]
        direction TB
        DataClient["🔌 Agent/MCPData Client"]
        MgmtClient["⚙️ ManagementClient"]
    end

    subgraph Gateway["MCP Gateway"]
        direction TB
        
        subgraph Auth1["Authentication & Authorization"]
            Auth["🔐 Data Plane AuthBearer Token / RBAC"]
            Auth2["🔐 Control Plane AuthBearer Token / RBAC"]
        end
        
        subgraph DataPlane["Data Plane"]