|
| 1 | +--- |
| 2 | +title: MCP Gateway |
| 3 | +description: "Docker's MCP Gateway provides secure, centralized, and scalable orchestration of AI tools through containerized MCP servers—empowering developers, operators, and security teams." |
| 4 | +keywords: MCP Gateway |
| 5 | +params: |
| 6 | + sidebar: |
| 7 | + group: Open source |
| 8 | +--- |
| 9 | + |
| 10 | +The MCP Gateway is Docker's open-source enterprise-ready solution for orchestrating and |
| 11 | +managing [Model Context Protocol (MCP)](https://spec.modelcontextprotocol.io/) servers |
| 12 | +securely across development and production environments. |
| 13 | +It is designed to help organizations connect MCP servers from the [Docker MCP Catalog](https://hub.docker.com/mcp) to MCP Clients without compromising security, visibility, or control. |
| 14 | + |
| 15 | +By unifying multiple MCP servers into a single, secure endpoint, the MCP Gateway offers |
| 16 | +the following benefits: |
| 17 | + |
| 18 | +- Secure by default: MCP servers run in isolated Docker containers with restricted |
| 19 | + privileges, network access, and resource usage. |
| 20 | +- Unified management: One gateway endpoint centralizes configuration, credentials, |
| 21 | + and access control for all MCP servers. |
| 22 | +- Enterprise observability: Built-in monitoring, logging, and filtering tools ensure |
| 23 | + full visibility and governance of AI tool activity. |
| 24 | + |
| 25 | +## Who is the MCP Gateway designed for? |
| 26 | + |
| 27 | +The MCP Gateway solves problems encountered by various groups: |
| 28 | + |
| 29 | +- Developers: Deploy MCP servers locally and in production using Docker Compose, |
| 30 | + with built-in support for protocol handling, credential management, and security policies. |
| 31 | +- Security teams: Achieve enterprise-grade isolation and visibility into AI tool |
| 32 | + behavior and access patterns. |
| 33 | +- Operators: Scale effortlessly from local development environments to production |
| 34 | + infrastructure with consistent, low-touch operations. |
| 35 | + |
| 36 | +## Key features |
| 37 | + |
| 38 | +- Server management: List, inspect, and call MCP tools, resources and prompts from multiple servers |
| 39 | +- Container-based servers: Run MCP servers as Docker containers with proper isolation |
| 40 | +- Secrets management: Secure handling of API keys and credentials via Docker Desktop |
| 41 | +- Server catalog: Manage and configure multiple MCP catalogs |
| 42 | +- Dynamic discovery and reloading: Automatic tool, prompt, and resource discovery from running servers |
| 43 | +- Monitoring: Built-in logging and call tracing capabilities |
| 44 | + |
| 45 | +## Install the MCP Gateway |
| 46 | + |
| 47 | +### Prerequisites |
| 48 | + |
| 49 | +- [Docker Engine](/manuals/engine/_index.md) |
| 50 | +- Go 1.24+ (for development) |
| 51 | + |
| 52 | +### Install using a pre-built binary |
| 53 | + |
| 54 | +> [!IMPORTANT] |
| 55 | +> These instructions are mostly suitable for testing purposes. |
| 56 | +> We otherwise recommend building from the sources. See the [README](https://github.com/docker/mcp-gateway?tab=readme-ov-file#installation). |
| 57 | +
|
| 58 | +You can download the latest binary from the [GitHub releases page](https://github.com/docker/mcp-gateway/releases/latest). |
| 59 | + |
| 60 | +Rename the relevant binary and copy it to the destination matching your OS: |
| 61 | + |
| 62 | +| OS | Binary name | Destination folder | |
| 63 | +|---------|---------------------|-------------------------------------| |
| 64 | +| Linux | `docker-mcp` | `$HOME/.docker/cli-plugins` | |
| 65 | +| macOS | `docker-mcp` | `$HOME/.docker/cli-plugins` | |
| 66 | +| Windows | `docker-mcp.exe` | `%USERPROFILE%\.docker\cli-plugins` | |
| 67 | + |
| 68 | +Or copy it into one of these folders for installing it system-wide: |
| 69 | + |
| 70 | + |
| 71 | +{{< tabs group="" >}} |
| 72 | +{{< tab name="On Unix environments">}} |
| 73 | + |
| 74 | + |
| 75 | +* `/usr/local/lib/docker/cli-plugins` OR `/usr/local/libexec/docker/cli-plugins` |
| 76 | +* `/usr/lib/docker/cli-plugins` OR `/usr/libexec/docker/cli-plugins` |
| 77 | + |
| 78 | +> [!NOTE] |
| 79 | +> You may have to make the binaries executable with `chmod +x`: |
| 80 | +
|
| 81 | +> ```bash |
| 82 | +> $ chmod +x ~/.docker/cli-plugins/docker-mcp |
| 83 | +> ``` |
| 84 | +
|
| 85 | +{{< /tab >}} |
| 86 | +{{< tab name="On Windows">}} |
| 87 | +
|
| 88 | +* `C:\ProgramData\Docker\cli-plugins` |
| 89 | +* `C:\Program Files\Docker\cli-plugins` |
| 90 | +
|
| 91 | +{{< /tab >}} |
| 92 | +{{</tabs >}} |
| 93 | +
|
| 94 | +You can now use the `mcp` command: |
| 95 | +
|
| 96 | +```bash |
| 97 | +docker mcp --help |
| 98 | +``` |
| 99 | +
|
| 100 | +## Use the MCP Gateway |
| 101 | + |
| 102 | +To view all the commands and configuration options, go to the [mcp-gateway repository](https://github.com/docker/mcp-gateway). |
| 103 | + |
| 104 | +## Related pages |
| 105 | + |
| 106 | +- [Docker MCP toolkit and catalog](/manuals/ai/mcp-catalog-and-toolkit/_index.md) |
0 commit comments