Docker for DevOps automation

Pick 4 of 4 for DevOps automationOfficialDocker

Docker is the fourth of four picks for DevOps automation, and the rank fits its scope: it operates the container layer, not the wider cloud. Docker's official MCP Gateway runs, secures, and aggregates containerized MCP servers behind one endpoint, with on-demand discovery from the Docker MCP Catalog, which is most useful for the container and local-environment layer of a build.

It sits last because DevOps automation here means provisioning and operating infrastructure across a cloud or orchestrator, where the siblings lead. Docker wins for managing the container runtime and for composing other MCP servers behind a single gateway.

How Docker fits

The Gateway's tools are about discovering and wiring servers rather than driving cloud resources directly. mcp-find searches the Docker MCP Catalog, mcp-add brings a discovered server into the session so its tools appear, mcp-config-set configures its secrets and options, and mcp-remove takes it back out. mcp-exec runs a tool on a server in the session, and the experimental code-mode creates a JavaScript-enabled tool that combines tools across servers.

The honest comparison: AWS (AWS Labs) covers a hyperscaler's full resource surface, Google Cloud Run handles serverless containers on GCP, and Kubernetes drives cluster operations directly. Those three provision and operate the infrastructure that DevOps automation usually means, which is why they rank ahead. Docker's Gateway is the layer that aggregates and secures the MCP servers an agent uses, and surfaces the container runtime, so reach for it to manage the container layer and to compose the other servers, not to provision a cloud.

Tools you would use

ToolWhat it does
mcp-findSearch for MCP servers in the Docker MCP Catalog by name or description.
mcp-addAdd a discovered MCP server to the current session so its tools become available.
mcp-config-setConfigure settings (such as secrets or options) for an MCP server in the session.
mcp-removeRemove an MCP server from the current session.
mcp-execExecute a tool by name that exists on a server in the current session.
code-modeExperimental: create a JavaScript-enabled tool that combines tools from multiple MCP servers.
Full Docker setup and config →

FAQ

Does Docker's MCP Gateway provision cloud infrastructure?
No. It runs, secures, and aggregates MCP servers behind one endpoint and surfaces the container layer. For provisioning a cloud or cluster, AWS (AWS Labs), Google Cloud Run, or Kubernetes are the picks; Docker composes the servers an agent uses.
What does the code-mode tool do?
It is an experimental tool that creates a JavaScript-enabled tool combining tools from multiple MCP servers in the session, useful for chaining actions across the servers the Gateway has aggregated.