Docker MCP vs Kubernetes MCP

Exposes the local Docker socket as tools: list containers, read logs, inspect images, start and stop services. Genuinely useful for local development, and dangerous enough that the socket access deserves a deliberate decision rather than a quick install. Talks to…

MCP Servers Verified 9 Nov
Install docker mcp gateway run npx -y kubernetes-mcp-server@latest
Source Official Official
Deciding factor The work is local development: start, stop, read logs,… versus: The work is operating a shared cluster, and the…
Bottom line

Local Docker is one machine's containers; Kubernetes is a cluster with its own permission model.

The short answer

Both expose container state to an agent, and the blast radius is not comparable. Docker's socket is effectively root on a single machine — acceptable on a laptop with disposable state, risky on a host that matters. Kubernetes access is mediated by RBAC and contexts, which is more governance but also more ways to point at the wrong cluster.

Facts

Option Install Source
Docker MCP docker mcp gateway run Repository ↗ Official
Kubernetes MCP npx -y kubernetes-mcp-server@latest Repository ↗ Official

Pick Docker MCP if

The work is local development: start, stop, read logs, inspect a container on the machine in front of you.

Pick Kubernetes MCP if

The work is operating a shared cluster, and the agent needs to read pods and events with a scoped service account.

What would change our mind

A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.

Read the full entries

More comparisons with these entries

All comparisons

More head-to-heads

All comparisons