Overview
What is Docker MCP Server?
The Docker MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Docker Desktop on Windows, enabling advanced automation and interaction capabilities for developers and tools.
How to use Docker MCP Server?
Install Docker Desktop for Windows and expose the daemon on tcp://localhost:2375 without TLS. Then configure the server in Claude Desktop by adding the provided JSON entry to mcpServers, which runs the Docker container freezeolo/docker-mcp-server via Docker CLI.
Key features of Docker MCP Server
- Container lifecycle management (create, start, stop, restart, remove, inspect)
- Network management (create, list, inspect, connect, disconnect, remove)
- Image management (list, pull, push, tag, build, remove, inspect)
- Container logs retrieval with filtering options
- Integration with Claude Desktop via MCP protocol
Use cases of Docker MCP Server
- Automate container creation, startup, and cleanup in development workflows
- Manage Docker networks and connect containers programmatically
- Build and push Docker images from a Dockerfile
- Retrieve and filter container logs for debugging
FAQ from Docker MCP Server
How do I install the project?
Follow the steps in the Installation section. Make sure you have the required dependencies — Docker Desktop for Windows with the daemon exposed on tcp://localhost:2375 without TLS.
What runtime or dependencies are required?
Docker Desktop for Windows is required. The server itself runs as a Docker container (freezeolo/docker-mcp-server) that communicates with the Docker daemon over HTTP.
How does the server communicate with Docker Desktop?
The server connects to Docker Desktop via the daemon exposed on tcp://localhost:2375 without TLS. You must enable this in Docker Desktop Settings > General.
Can I verify the daemon is accessible?
Open http://localhost:2375/version in your browser. A JSON response with Docker version information confirms the setup is correct.
Does the server require authentication or special transport?
No authentication or special transport is mentioned. It uses standard HTTP to the Docker daemon and connects via the MCP stdio transport when launched through Claude Desktop.
