MCP Gateway

Name: MCP Gateway
Author: IBM

@IBM

关于 MCP Gateway

An AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.

基本信息

分类

其他

许可证

Apache-2.0

运行时

python

传输方式

stdio

发布者

IBM

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mcp-context-forge": {
      "command": "uvx",
      "args": [
        "--from",
        "mcp-contextforge-gateway",
        "mcpgateway",
        "--host",
        "0.0.0.0",
        "--port",
        "4444"
      ]
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is MCP Gateway?

MCP Gateway is an open source registry and proxy that federates Model Context Protocol (MCP) servers, A2A agents, and REST/gRPC APIs into a single unified endpoint. It provides centralized governance, discovery, observability, and protocol translation for AI clients.

How to use MCP Gateway?

Install the mcp-contextforge-gateway package via PyPI or use the Docker image. Configure settings through a .env file or environment variables, then launch the server with the mcpgateway command. A quick start using uvx is also supported.

Key features of MCP Gateway

Federation across MCP, A2A, REST, and gRPC services
REST-to-MCP and gRPC-to-MCP automatic tool translation
Built-in auth, rate-limiting, retries, and OAuth token support
Admin UI for real-time configuration and log monitoring
OpenTelemetry observability with Phoenix, Jaeger, Zipkin, and other backends
Redis-backed caching and multi-cluster federation for scalability

Use cases of MCP Gateway

Federating multiple MCP servers under a single gateway for AI agents
Exposing legacy REST or gRPC APIs as MCP-compliant tools without code changes
Routing agent-to-agent (A2A) requests across OpenAI, Anthropic, or custom agents
Centralizing governance, auth, and observability for enterprise AI infrastructure
Airgapped deployments with a bundled Admin UI and offline capability

FAQ from MCP Gateway

What are the prerequisites to run MCP Gateway?

Python ≥ 3.11 is required. For quick-start smoke tests, curl and jq are recommended.

How do I authenticate with the gateway?

MCP Gateway supports Basic auth, JWT tokens, and OAuth tokens scoped per user. An X-Upstream-Authorization header can be set unconditionally for backend services.

What transports does MCP Gateway support?

It supports HTTP, JSON-RPC, WebSocket, SSE (with configurable keepalive), stdio, and streamable-HTTP.

Does MCP Gateway support OpenTelemetry?

Yes. It provides vendor-agnostic tracing via OTLP protocol and works with Phoenix, Jaeger, Zipkin, Tempo, DataDog, and New Relic backends.

Where is data stored?

MCP Gateway uses Redis for caching and federation. There is no embedded database; configuration and state are managed via files, environment variables, and Redis.