Docker for Kubernetes and containers
Docker is the second of three picks for Kubernetes and containers, the container-runtime entry point for the set. Docker's official MCP Gateway runs, secures, and aggregates containerized MCP servers behind one endpoint, with on-demand discovery from the Docker MCP Catalog, so an agent can find and wire in container-related servers from one place.
It ranks behind the native Kubernetes client, which is the direct line to cluster operations like listing pods and reading logs, but ahead of the GitOps controller for this task. Docker's role is the runtime and the gateway that aggregates the servers an agent uses.
How Docker fits
The Gateway tools handle discovery and execution. mcp-find searches the Docker MCP Catalog for a server by name or description, mcp-add brings it into the session so its tools become available, mcp-config-set configures its secrets and options, and mcp-remove takes it out. mcp-exec runs a named tool on a session server, and the experimental code-mode creates a JavaScript-enabled tool that combines tools across servers, useful when a container task spans several.
The honest framing: the urgent container questions, which pods are crash-looping, what the logs say, are answered most directly by the native Kubernetes server, which is why it leads. Argo CD is the GitOps controller for reconciling declared state against what is actually deployed. Docker's Gateway is the runtime entry point and the aggregation layer, so pair it with the Kubernetes server for cluster operations and use Docker to discover, secure, and compose the container tooling an agent reaches for.
Tools you would use
| Tool | What it does |
|---|---|
| mcp-find | Search for MCP servers in the Docker MCP Catalog by name or description. |
| mcp-add | Add a discovered MCP server to the current session so its tools become available. |
| mcp-config-set | Configure settings (such as secrets or options) for an MCP server in the session. |
| mcp-remove | Remove an MCP server from the current session. |
| mcp-exec | Execute a tool by name that exists on a server in the current session. |
| code-mode | Experimental: create a JavaScript-enabled tool that combines tools from multiple MCP servers. |
FAQ
- Does Docker's Gateway replace a Kubernetes MCP server?
- No. The native Kubernetes server is the direct line to cluster operations like listing pods and reading logs, and it leads this task. Docker's Gateway aggregates and secures container MCP servers and surfaces the runtime.
- How does an agent add a container tool through Docker's Gateway?
- It uses mcp-find to search the Docker MCP Catalog, mcp-add to bring the server into the session, mcp-config-set for its options, then mcp-exec to run a tool on it.