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.
Implements gRPC-to-MCP translation via server reflection and REST-to-MCP adaptation with automatic JSON Schema extraction, while providing OpenTelemetry-based observability across multiple backends (Phoenix, Jaeger, Zipkin). Runs as a native MCP server with 40+ plugins for protocol extensibility, Redis-backed caching for multi-cluster deployments, and built-in auth, rate-limiting, and retry policies across federated tool, agent, and API gateways.
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.
Implements a unified registry and gateway for both MCP servers and AI agents, enabling dynamic tool discovery and agent-to-agent communication through the A2A Protocol while maintaining centralized credential management and audit trails. Supports multi-protocol agent communication patterns with streamable HTTP transport for cloud-hosted infrastructure, integrating external registries like Anthropic's MCP Registry into a single control plane for governance across tools and agents.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work