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
eznix86/mcp-gateway
Too much tools in context. Use a gateway
# Technical Summary Aggregates multiple Model Context Protocol (MCP) servers through a unified gateway that indexes all upstream tools and exposes them via `gateway.search`, `gateway.describe`, and `gateway.invoke` endpoints, reducing initial token usage by ~40%. Operates as both MCP client (connecting to upstream servers via stdio, HTTP, or WebSocket) and MCP server, with an in-memory tool catalog and job queue for async operations. Integrates with Claude Code, OpenCode, and other MCP clients through stdio transport or HTTP/WebSocket endpoints, supporting local server spawning and remote server connections via configuration file.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work