mcp-context-forge and mcp-center
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-center
nautilus-ops/mcp-center
A centralized platform for managing and connecting MCP servers. MCP Center provides a high-performance proxy service that enables seamless communication between MCP clients and multiple MCP servers.
Built in Rust with Axum, it proxies both SSE and Streamable MCP transports while providing unified service discovery and authentication across distributed MCP servers in Kubernetes environments. The platform uses PostgreSQL-backed registries for server management and includes a plugin system for parameter filtering and tool-level traceability, eliminating per-server ingress configuration overhead.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work