Unla and mcp-gateway
These are complementary tools: Unla provides a lightweight gateway to expose existing MCP servers and APIs, while mcp-gateway serves as a central registry and management hub that can orchestrate multiple MCP servers and translate REST APIs into MCP protocol, making them useful together in a layered MCP infrastructure.
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
theognis1002/mcp-gateway
Model Context Protocol (MCP) Gateway & Registry - Central hub for managing tools, resources, and prompts for MCP-compatible LLMs. Translates REST APIs into MCP, builds virtual MCP servers with security and observability, and bridges multiple transports (stdio, SSE, streamable HTTP).
Built in Go with PostgreSQL and Redis backing, the gateway enforces fine-grained access control through JWT/OAuth2 authentication, RBAC policies, and content filtering—enabling secure multi-tenant namespaces where AI agents access isolated server groups. It implements automatic server discovery and health monitoring with failover capabilities, while supporting JSON-RPC 2.0, WebSocket, Server-Sent Events, and streamable HTTP transports to bridge diverse client needs with comprehensive audit logging and performance metrics.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work