I
IBM/mcp-context-forge
Gateway and registry in front of MCP, A2A and REST APIs
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"ibm-mcp-context-forge": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"]
}
}
}解析自我们于 2026-11-04 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"ibm-mcp-context-forge": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio ibm-mcp-context-forge -- npx -y @modelcontextprotocol/inspector
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
- 安装
npx -y @modelcontextprotocol/inspector
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -y @modelcontextprotocol/inspector。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-11-05；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# ContextForge
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
> An open source registry and proxy that federates MCP, A2A, and REST/gRPC APIs with centralized governance, discovery, and observability. Optimizes Agent & Tool calling, and supports plugins.
ContextForge is an open source registry and proxy that federates tools, agents, and APIs into one clean endpoint for your AI clients. It provides centralized governance, discovery, and observability across your AI infrastructure:
Tools Gateway — MCP, REST, gRPC-to-MCP translation, and TOON compression
Agent Gateway — A2A protocol, OpenAI-compatible and Anthropic agent routing
API Gateway — Rate limiting, auth, retries, and reverse proxy for REST services
Plugin Extensibility — 40+ plugins for additional transports, protocols, and integrations
Observability — OpenTelemetry tracing with Phoenix, Jaeger, Zipkin, and other OTLP backends
It runs as a fully compliant MCP server, deployable via PyPI or Docker, and scales to multi-cluster environments on Kubernetes with Redis-backed federation and caching.
## Table of Contents
Overview & Goals
Quick Start - PyPI
Quick Start - Containers
Optional Web UI
VS Code Dev Container
Installation
Upgrading
Configuration
Running
Cloud Deployment
API Reference
Testing
Project Structure
Development
Troubleshooting
Contributing
### 📌 Quick Links
| Resource | Description |
| 5-Minute Setup | Get started fast — uvx, Docker, Compose, or local dev |
| Getting Help | Support options, FAQ, community channels |
| Issue Guide | How to file bugs, request features, contribute |
| Full Documentation | Complete guides, tutorials, API reference |
| Deprecations | Deprecated runtime paths and migration guidance |
## Overview & Goals
ContextForge is an open source registry and proxy that federates any Model Context Protocol (MCP) server, A2A server, or REST/gRPC API, providing centralized governance, discovery, and observability. It optimizes agent and tool calling, and supports plugins. See the project roadmap for more details.
It currently supports:
Federation across multiple MCP and REST services
A2A (Agent-to-Agent) integration for external AI agents (OpenAI, Anthropic, custom)
gRPC-to-MCP translation via automatic reflection-based service discovery
Virtualization of legacy APIs as MCP-compliant tools and servers
Transport over HTTP, JSON-RPC, WebSocket, SSE (with configurable keepalive), and Streamable HTTP; stdio transport available for server-side use
An Admin UI for real-time management, configuration, and log monitoring (with airgapped deployment support)
A redesigned, more user-friendly Web UI that runs in a separate container
Built-in auth, retries, and rate-limiting with user-scoped OAuth tokens and unconditional X-Upstream-Authorization header support
OpenTelemetry observability with Phoenix, Jaeger, Zipkin, and other OTLP backends
Scalable deployments via Docker or PyPI, Redis-backed caching, and multi-cluster federation
For a list of upcoming features, check out the ContextForge Roadmap
🔌 Gateway Layer with Protocol Flexibility
Federates any MCP server or REST API
Lets you choose your MCP protocol version (e.g., 2025-11-25)
Exposes a single, unified interface for diverse backends
ContextForge is an open source registry and proxy that federates tools, agents, and APIs into one clean endpoint for your AI clients. It provides centralized governance, discovery, and observability across your AI infrastructure:
Tools Gateway — MCP, REST, gRPC-to-MCP translation, and TOON compression
Agent Gateway — A2A protocol, OpenAI-compatible and Anthropic agent routing
API Gateway — Rate limiting, auth, retries, and reverse proxy for REST services
Plugin Extensibility — 40+ plugins for additional transports, protocols, and integrations
Observability — OpenTelemetry tracing with Phoenix, Jaeger, Zipkin, and other OTLP backends
It runs as a fully compliant MCP server, deployable via PyPI or Docker, and scales to multi-cluster environments on Kubernetes with Redis-backed federation and caching.
## Table of Contents
Overview & Goals
Quick Start - PyPI
Quick Start - Containers
Optional Web UI
VS Code Dev Container
Installation
Upgrading
Configuration
Running
Cloud Deployment
API Reference
Testing
Project Structure
Development
Troubleshooting
Contributing
### 📌 Quick Links
| Resource | Description |
| 5-Minute Setup | Get started fast — uvx, Docker, Compose, or local dev |
| Getting Help | Support options, FAQ, community channels |
| Issue Guide | How to file bugs, request features, contribute |
| Full Documentation | Complete guides, tutorials, API reference |
| Deprecations | Deprecated runtime paths and migration guidance |
## Overview & Goals
ContextForge is an open source registry and proxy that federates any Model Context Protocol (MCP) server, A2A server, or REST/gRPC API, providing centralized governance, discovery, and observability. It optimizes agent and tool calling, and supports plugins. See the project roadmap for more details.
It currently supports:
Federation across multiple MCP and REST services
A2A (Agent-to-Agent) integration for external AI agents (OpenAI, Anthropic, custom)
gRPC-to-MCP translation via automatic reflection-based service discovery
Virtualization of legacy APIs as MCP-compliant tools and servers
Transport over HTTP, JSON-RPC, WebSocket, SSE (with configurable keepalive), and Streamable HTTP; stdio transport available for server-side use
An Admin UI for real-time management, configuration, and log monitoring (with airgapped deployment support)
A redesigned, more user-friendly Web UI that runs in a separate container
Built-in auth, retries, and rate-limiting with user-scoped OAuth tokens and unconditional X-Upstream-Authorization header support
OpenTelemetry observability with Phoenix, Jaeger, Zipkin, and other OTLP backends
Scalable deployments via Docker or PyPI, Redis-backed caching, and multi-cluster federation
For a list of upcoming features, check out the ContextForge Roadmap
🔌 Gateway Layer with Protocol Flexibility
Federates any MCP server or REST API
Lets you choose your MCP protocol version (e.g., 2025-11-25)
Exposes a single, unified interface for diverse backends
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/ibm-mcp-context-forge/)
- 来源
- awesome · https://github.com/IBM/mcp-context-forge
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。