Skip to content

MCP setupDevOps and cloud

Docker MCP Gateway

Route your agent through Docker's MCP gateway so each tool server runs in its own isolated container with secrets kept out of env variables.

npx workspacetemplates add docker-mcp --tool claude-code

Writes 1 file to your project root

.mcp.jsonmerge into your file12 lines · 147 BFile
{
  "mcpServers": {
    "docker": {
      "command": "docker",
      "args": [
        "mcp",
        "gateway",
        "run"
      ]
    }
  }
}

What it does

The Docker MCP gateway sits between your coding agent and a set of MCP servers. Instead of starting each server yourself, you pick them in a profile and the gateway runs the local ones in separate containers, with minimal access to your machine.

Your agent sees one server and the gateway handles the rest. You can also turn individual tools on or off per profile, which is a simple way to keep a risky tool out of reach. It needs Docker Desktop 4.59 or later with the MCP Toolkit enabled.

Example

you › List the tools you can reach through the Docker gateway and say which server each one comes from.

agent › 12 tools from 3 servers in the default profile: fetch (1 tool), github (9 tools) and duckduckgo (2 tools). Each runs in its own container.

Questions

Which servers does the agent get?
Those in the profile you run. With no flag it uses the default profile. Add --profile name to the args to pick another.
Does it work without Docker Desktop?
Outside Docker Desktop you first run docker mcp feature enable profiles, as the repository describes.
Where do server secrets go?
The gateway uses Docker Desktop's secrets handling, so you do not put tokens in the agent config.
  • AWS Documentation MCP Server

    MCP setupDevOps and cloud

    Free
  • Azure MCP Server

    MCP setupDevOps and cloud

    Free
  • CircleCI MCP Server

    MCP setupDevOps and cloud

    Free
  • Cloudflare MCP Server

    MCP setupDevOps and cloud

    Free