mcp-context-forge and mcp-gateway
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
aarora79/mcp-gateway
MCP Gateway and Registry
Provides centralized access to multiple Model Context Protocol (MCP) servers through an Nginx reverse proxy, enabling AI agents to discover and invoke tools dynamically across distributed backends. The Registry component offers both UI and programmatic interfaces for service discovery, health monitoring, and dynamic tool exploration via natural language queries. Supports multiple transport mechanisms (SSE and Streamable HTTP) with deployments spanning EC2 instances, EKS clusters, and AWS Lambda functions.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work