One Endpoint for Every MCP Server, Agent, and API: Inside IBM's ContextForge

ContextForge is IBM's MCP gateway. Register your MCP servers, A2A agents and REST endpoints in one catalog, then bundle the tools one agent needs into a virtual server it reaches as a single endpoint. Tool lists are filtered by team before the client receives them, so scoping stops being each server's private decision. 4,185 stars, Apache-2.0.

Mostly accurate, one number is stale.

• "IBM's MCP gateway" — correct. ContextForge is an open source registry and proxy that federates tools, agents, and APIs into one clean endpoint for AI clients, maintained under IBM's GitHub org.
• Register MCP servers, A2A agents, and REST endpoints in one catalog — accurate. It supports federation across multiple MCP and REST services, A2A integration for external AI agents, gRPC-to-MCP translation, and virtualization of legacy APIs as MCP-compliant tools and servers.
• Bundle tools into a virtual server reached as a single endpoint — accurate. The project's own quickstart walks through registering a server, then creating a "virtual server" that bundles selected tool IDs and exposes them at a single unified endpoint.
• Apache-2.0 — confirmed license.
• "Tool lists are filtered by team before the client receives them" — plausible given the product's RBAC and team-scoping features, but I couldn't fully verify this exact mechanism independently — reasonably likely, not fully confirmed.
• Star count is outdated: the repo currently shows 3.7k stars, not 4,185. It may have been accurate at an earlier point, but as of now it's off — worth updating before you post.