Gateway MCP Server
Docker container-based MCP server management and unified tool gateway access.
Data last scanned today · Reviewed today
Overview
Gateway MCP Server acts as a CLI plugin for Docker Desktop, providing a centralized infrastructure to manage, run, and deploy Model Context Protocol servers. It abstracts the lifecycle of MCP tools by running each server within an isolated Docker container, ensuring consistent access across various AI clients. Beyond simple orchestration, the platform offers built-in secrets management and OAuth flow support, allowing developers to handle sensitive credentials securely without relying on raw environment variables. It also features dynamic tool discovery, enabling AI models to automatically identify and interact with available resources, prompts, and tools across multiple configured catalogs.
Our verdict
With a security score of 50/100, this server is currently classified as high-risk. This rating is driven by the fact that critical security aspects such as read-only mode enforcement and authentication implementation methods have not yet been editorially reviewed. Given these unverified security boundaries, it is best suited for development and prototyping environments rather than production systems handling sensitive data.
- Isolated execution environment using Docker containers
- Zero direct dependencies reduces supply chain attack surface
- Integrated support for secure OAuth authentication flows
- Active development with a 12-day last commit frequency
- Authentication implementation methods remain unreviewed
- Read-only capabilities have not been editorially verified
- Community-maintained rather than official vendor-backed software
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the core prerequisites to use the Gateway MCP Server?
You need Docker Desktop 4.59+ with the MCP Toolkit feature enabled. For development purposes, Go 1.24+ is required.
›Can I run the MCP gateway outside of Docker Desktop?
Yes, you can use it with Docker CE, in WSL2, or in containerized environments by setting the environment variable DOCKER_MCP_IN_CONTAINER=1 and enabling the profiles feature via the CLI.
›How are API keys and credentials managed for MCP servers?
The gateway utilizes Docker Desktop's built-in secrets management to keep credentials and API keys out of your environment variables.
›What types of server sources can I use within an MCP profile?
Profiles support four types of sources: catalog references from the Docker MCP Catalog, OCI image references, direct MCP registry references, and local file references.
›How do I ensure my MCP configurations are consistent across different AI clients?
By connecting your AI clients like VS Code, Cursor, or Claude Desktop to the single Gateway configuration, you ensure consistent tool access and settings across all connected applications.
›Is there a way to share my configured MCP profiles with others?
Yes, you can export profiles to a YAML file or push them to an OCI registry to share or transfer them between environments.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.