Open Source Go MCP Gateways

kgateway is a mature, cloud-native API and ingress gateway designed to provide unified API connectivity for services, microservices, serverless workloads, and AI-centric systems running on Kubernetes clusters. It implements the Kubernetes Gateway API and can operate as both a lightweight in-cluster microgateway and a centralized gateway capable of handling billions of API calls with high performance and low latency. By integrating with Envoy and advanced data planes, it handles modern ingress concerns such as traffic routing, authentication, authorization, rate limiting, and observability for traditional HTTP/gRPC services and AI workloads alike. Beyond standard API traffic, kgateway also supports gateway patterns tailored for large language model (LLM) consumption, inference routing, and Model Context Protocol (MCP) orchestration, enabling secure access to models, tools, and agent interactions.

Bifrost is an LLM gateway designed to provide a unified OpenAI-compatible API front for many different model providers. It abstracts away the complexity of working directly with multiple backend providers (OpenAI, Anthropic, AWS Bedrock, Google Vertex, etc.), enabling you to plug in providers and switch between them without touching your client code. It is built to be high performance: in benchmark tests at 5,000 requests per second, it reportedly adds only microseconds of overhead and achieves perfect success rates with no failed requests. Bifrost supports features such as automatic fallback (failover between providers), load balancing across API keys/providers, and semantic caching to reduce latency and cost. It also includes observability with built-in metrics, tracing, logging, and supports governance features like rate limiting, access control, and cost budgeting. The architecture is modular: there is a core engine, plugin layers, and transport layers (HTTP APIs).

Obot is an open-source platform built to help organizations adopt and operate Model Context Protocol (MCP) capabilities in a centralized, production-friendly way. It combines multiple MCP building blocks into one system, including hosting for MCP servers, a registry for discovery, a gateway layer to route access, and a standards-compliant chat client experience. The project is aimed at solving common enterprise rollout problems such as reliably hosting servers for internal and external users, curating “approved” MCP servers for employees to find, and enforcing authentication, access control, and auditable activity. It also supports building richer agents and chatbots that can leverage MCP servers while keeping operations manageable for IT and platform teams. The platform is designed to work with a variety of workflows and clients, so MCP servers managed inside Obot can be used by automation/agent frameworks as well as popular chat clients that speak MCP.

Docker’s MCP Gateway project is a Docker CLI plugin and supporting gateway system designed to run, manage, and securely expose MCP servers using container isolation. It underpins the MCP Toolkit experience in Docker Desktop, but it can also be used independently as a general-purpose MCP operational layer. The core idea is to treat MCP servers like containerized services, giving each server controlled privileges and a lifecycle you can inspect, enable/disable, and reset as needed. Instead of having each AI client manage its own MCP server configuration, the gateway provides a unified interface so multiple clients can connect consistently to the same configured tool surface. The project emphasizes security and operational hygiene by supporting secrets management (to avoid leaking credentials via plain environment variables) and providing built-in OAuth flows for MCP servers that require authenticated service access.

Octelium is an open source, self-hosted unified secure-access platform built for modern infrastructure and hybrid environments. It positions itself as more than a typical VPN; it supports zero-trust network access (ZTNA), “BeyondCorp”-style access, API/AI gateway functionality, and even serves as a PaaS-like deployment surface. One of its key strengths is identity-based, application-layer (L7) aware control, meaning access decisions are made per request, with context and policy rather than simple network-level allow/block rules. It supports both client-based (e.g., WireGuard/QUIC tunnels) and client-less access models, which makes it flexible for both human users and automated workloads. The project also highlights self-hosted, no hidden “server-side” locked components, giving organizations greater ownership and control over access, rather than relying on proprietary SaaS.

HasMCP empowers AI development by seamlessly connecting your existing APIs to Large Language Models. Its Automated OpenAPI Mapping instantly translates API documentation into LLM-usable tools, eliminating manual coding. Security is paramount, with Native MCP Elicitation Auth managing complex authentication flows like OAuth2, ensuring user credentials are never exposed. To enhance efficiency, Context Window Optimization intelligently prunes API responses using JMESPath and Goja (JS) logic, dramatically reducing costs and improving response times. The platform is built for dynamic environments; Real-time Dynamic Tooling allows the system to adapt on the fly as APIs change or go offline. For robust security, it includes Secure Secret & Gateway Management to safeguard sensitive credentials in an encrypted vault. MCP Composition enables the construction of high-performance, modular AI systems. Finally, comprehensive Observability & Telemetry tools offer deep insights into tool usages.

MCPJungle is a self-hosted gateway and registry for the Model Context Protocol (MCP), aimed at managing tool/integration servers for AI agents within organizations. It offers a “single source of truth” registry where developers can register MCP servers and the tools they provide, and MCP clients (such as AI agents) discover and consume those tools through one gateway endpoint. This greatly simplifies the architecture when you have many MCP servers; agents only need to connect to one gateway rather than multiple endpoints. The platform supports enterprise-grade workflows; centralized tool management, access control, self-hosting so that internal servers and tools remain under your organization’s control, and registry metadata to track what tools exist and who can use them. For organizations building internal AI automation systems, MCPJungle helps enforce governance, tool discovery, and integration scalability.