Open Source BSD MCP Gateways

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.

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.

Gate22 is an open-source governance and control plane for Model Context Protocol (MCP) environments that helps teams define and enforce policies about which tools and capabilities AI agents can access, how they can interact with those tools, and how usage is logged and audited. It provides a centralized layer where organizations can configure permission boundaries, role-based access, and operational constraints that govern agent behavior and tool invocation across agentic IDEs or custom agent stacks. By integrating with MCP-aware systems, Gate22 helps maintain security and compliance while enabling teams to scale agent-enabled workflows without losing observability into what actions are taken and why. It can be used to enforce fine-grained policies that restrict dangerous or unauthorized operations, track which agents are calling which tools, and record metadata for auditing and debugging.

Unla is a lightweight, highly available MCP gateway written in Go that turns existing MCP servers or ordinary HTTP APIs into MCP-compliant services through configuration, not code changes. Its goal is to let teams “wire up” tools they already run—internal REST endpoints, third-party APIs, or local MCP servers—and present a single, reliable MCP interface to clients like Claude Desktop, Cursor, and IDEs. The gateway focuses on operational concerns you’d expect in production: multi-instance availability, health checking, and declarative routing that maps upstreams to MCP tools and resources. A quick-start and CLI make it easy to stand up an API server, while the package structure exposes helpers for people who want to embed or extend the gateway. Because it is itself MCP-speaking, Unla can sit in front of mixed fleets and normalize transports and schemas for clients. Documentation and pkg.go.dev pages reinforce the positioning as a stable, Go-native building block for MCP deployments.

Portkey AI Gateway aims to offer a blazing fast, secure, and flexible gateway for interacting with a wide variety of models and enforcing guardrails. It presents a single, friendly API through which you can route to 200+ LLMs, while applying configurable input/output guardrails to enforce policies or restrict certain content. It supports automatic retries, fallbacks, load balancing across providers or keys, and request timeouts to avoid latency spikes. The gateway is multimodal: it can handle text, vision, audio, and image models under a common interface. It also offers features for governance: role-based access, compliance with standards (SOC2, HIPAA, GDPR), secure key management, and logging/analytics of usage, latency, errors, and cost. The system integrates with agent frameworks like LangChain, Autogen, and others, enabling the building of more complex AI applications. It’s lightweight and optimized for low latency with a small footprint.

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).

DeployStack is an open-source framework that helps developers and teams define and deploy production infrastructure stacks using modular, reusable templates, often with IaC (infrastructure as code) principles. It provides a structured way to compose resources such as cloud networking, compute, and managed services into coherent deployment blueprints that can be versioned and reused across projects. By abstracting common deployment patterns and capturing them as templates, Deploystack reduces duplication of effort that typically occurs when setting up stacks for different applications or environments. The project emphasizes repeatability and clarity, enabling teams to follow best practices for scalability, security, and operational reliability without hand-crafting deployment scripts for every new service. It supports integration with popular cloud providers and infrastructure tooling, streamlining workflows that span local development through staging and production environments.

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.

MetaMCP is an all-in-one MCP aggregator, orchestrator, and middleware that merges many MCP servers into a single, policy-aware server you can point any MCP client at. It’s built to centralize discovery, apply middlewares (e.g., auth, rate limits, transforms), and present a unified catalog of tools and resources from diverse backends. The repository and site describe it as “the one MCP to manage all your MCPs,” with diagrams and examples showing how to compose fleets behind a single endpoint. It ships Dockerized for quick deployment and emphasizes dynamic aggregation so teams can register or remove servers without restarting clients. The org maintains related repos and a GUI app for cloud and self-hosted setups, with a note that the cloud demo is outdated while the open-source v2 evolves. Overall, MetaMCP aims to simplify multi-server MCP operations for individuals and organizations.