mcp-context-forge and mcp-gateway-registry
These are complements—mcp-context-forge provides the gateway infrastructure and proxy layer, while mcp-gateway-registry supplies the centralized discovery and registration backend that the gateway queries to expose unified tool endpoints.
About mcp-context-forge
IBM/mcp-context-forge
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.
This project helps AI developers and architects consolidate various AI agents, tools, and APIs into a single, managed access point. It takes disparate communication protocols (like MCP, A2A, REST, gRPC) and presents them as a unified, governed endpoint. This allows developers to easily integrate and manage diverse AI capabilities within their applications.
About mcp-gateway-registry
agentic-community/mcp-gateway-registry
Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI agents and AI coding assistants. Transform scattered MCP server chaos into governed, auditable tool access with Keycloak/Entra integration.
This platform helps AI development teams centralize access to their AI development tools and autonomous AI agents. It takes a chaotic collection of individual tool configurations and agent connections and turns them into a secure, governed, and easily discoverable system. AI platform engineers and enterprise architects can use this to manage all their AI development resources in one place.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work