
by L337
docker-mcp-server lets AI agents manage Docker containers, images, networks, volumes, swarm and more through typed MCP tools. It can manage several local or remote daemons in one session.
PluginContact for pricing
Step 1: Make sure a Docker daemon is reachable and uv is installed, or choose the container or .mcpb install.
Step 2: Add a docker-mcp-server entry to your MCP client config that runs uvx docker-mcp-server.
Step 3: Optionally set Docker host(s) for remote daemons, and enable read-only or no-destructive mode.
Step 4: Ask your agent about container state, logs or disk usage.
Step 5: Exclude unused tool domains if your client loads all tools eagerly.
Yes. It can manage remote daemons over SSH, TLS or TCP, though some features require SSH.
Yes. Read-only and no-destructive modes prevent write or destructive tools from being registered, and individual daemons can be marked read-only.
No. The README says it runs on your machine and sends no telemetry.
Requirements
Drop2Run MCPDrop2Run MCP lets an AI assistant publish a page, a folder of documents or a built site as an HTTPS link. It is the MCP route into the Drop2Run hosting service at dropto.run.
KNX Auditor MCPA design-time KNX and ETS6 assistant exposed as an MCP server. It designs, audits and repairs KNX projects and generates Home Assistant configuration, without access to the live bus.