Search Results for "layer"

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

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

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