mcp-context-forge and Unla
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 Unla
AmoyLab/Unla
🧩 MCP Gateway - A lightweight gateway service that instantly transforms existing MCP Servers and APIs into MCP servers with zero code changes. Features Docker deployment and management UI, requiring no infrastructure modifications.
Supports dynamic configuration hot-reloading via OS signals, HTTP, or Redis PubSub, enabling runtime updates without service restarts. Built in Go for minimal resource overhead, it bridges RESTful APIs and existing MCP servers to MCP-compliant endpoints using YAML-driven configuration, with multi-tenant session management and OAuth pre-authentication support. Includes persistent storage options (SQLite, PostgreSQL, MySQL) and native Kubernetes/Helm deployment support alongside Docker.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work