Unla and mcp-gateway
These are competitors offering similar MCP gateway solutions, with A providing a more feature-complete implementation (Docker, UI, wrapper functionality) while B appears to be a lighter-weight alternative addressing context overflow in tool-heavy MCP setups.
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.
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