mcp-context-forge
ContextForge (MCP Gateway) is a gateway, registry and proxy that sits in front of any MCP server, A2A server or REST API and exposes one unified endpoint for all your AI clients. According to the README it supports federation across multiple MCP and REST services, A2A integration for external AI agents (OpenAI, Anthropic or custom), gRPC-to-MCP translation by reflection-based discovery, virtualisation of legacy APIs as MCP tools and servers, and many transports (HTTP, JSON-RPC, WebSocket, SSE, stdio and streamable HTTP).
It adds an Admin UI for real-time management, configuration and log monitoring (with air-gapped support), built-in authentication, retries and rate limiting with user-scoped OAuth tokens, OpenTelemetry observability to Phoenix, Jaeger, Zipkin and other backends, and scalable deployment through Docker or PyPI with Redis-backed caching and multi-cluster federation. Since v0.7.0 it has multi-tenancy with email authentication, teams, RBAC and resource visibility. Quick starts cover PyPI, Docker, Docker Compose and Helm, and the README points to a SECURITY.md. The project is Apache-2.0 licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-23
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 7
- Latest release
- v1.1.0 (2026-10-20)
- Open issues
- 996
- Recent issues with at least one comment
- 5/21
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #5437 Human in the loop Approval for tool execution13 comments · 2026-06-30
- #5694 [FEATURE] ICA Metering Exporter Plugin — export MCP tool invocation metrics to ICA core-services9 comments · 2026-07-17
- #5043 [BUG]: Gateway OAuth Stores Token Per Admin User Instead of Per End-User9 comments · 2026-06-03
- #5731 [UI]: ContextForge TUI7 comments · 2026-07-21
- #5046 [FEATURE]: Granular (per-MCP-server) TOOL_DESCRIPTION_FORBIDDEN_PATTERNS with per-tool allowlisting6 comments · 2026-06-04
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You need one gateway in front of MCP servers, A2A agents and REST or gRPC services, with federation and virtual servers.
- You want to wrap REST or gRPC services as MCP tools so MCP clients can use non-MCP backends.
- You need multi-tenancy with RBAC, rate limiting, OpenTelemetry tracing and an admin UI, deployed by PyPI, Docker, Compose or Helm.
- You want a small tool: it is broad infrastructure (gateway, registry, proxy, admin UI, multi-tenancy) that you must deploy, secure and operate.
- You are upgrading from before v0.7.0: the README requires following a migration guide.
- You want to find setup steps quickly: the README is over 160,000 characters.
How it differs
Both are Apache-2.0 gateways with MCP federation and A2A support. ContextForge adds a registry, REST and gRPC wrapping and an admin UI. Agentgateway also routes LLM traffic with spend controls and guardrails.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!