by Swartdraak
Docker MCP Server — AI-driven Docker container management and automation; manage containers, images, networks, and volum
Provides direct control over Docker operations through AI assistants, allowing you to manage containers, images, and other Docker resources without switching to command line.
Docker MCP Server is a community-built MCP server published by Swartdraak that provides AI assistants with tools and capabilities via the Model Context Protocol. Docker MCP Server — AI-driven Docker container management and automation; manage containers, images, networks, and volum It is categorized under developer tools. This server exposes 37 tools that AI clients can invoke during conversations and coding sessions.
You can install Docker MCP Server in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Docker MCP Server is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Docker MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Docker MCP Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Docker MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Docker MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Docker MCP Server against two servers with overlapping tools; this profile had the clearer scope statement.
Docker MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired Docker MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Docker MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: Docker MCP Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Docker MCP Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 49
A comprehensive, production-ready, industry-standard compliant MCP (Model Context Protocol) Server that enables full Docker management capabilities for AI assistants like GitHub Copilot and Claude. Featuring 37 powerful tools covering containers, images, networks, volumes, and system operations.
Docker MCP Server is a Model Context Protocol server that bridges AI assistants with Docker, enabling natural language Docker operations. Built with TypeScript and following industry best practices, it provides a complete Docker management solution for AI-powered development workflows.
# Install globally
npm install -g @swartdraak/docker-mcp-server
# Or use with npx (no installation needed)
npx @swartdraak/docker-mcp-server
# Clone the repository
git clone https://github.com/Swartdraak/Docker-MCP.git
cd Docker-MCP
# Install dependencies
npm install
# Build the project
npm run build
# Start the server
npm start
npm install -g @swartdraak/docker-mcp-server
git clone https://github.com/Swartdraak/Docker-MCP.git
cd Docker-MCP
npm install
npm run build
Run the server directly:
npm start
The MCP server supports connecting to remote Docker hosts using environment variables:
DOCKER_HOST=tcp://192.168.1.100:2375 npm start
DOCKER_HOST=https://192.168.1.100:2376 \
DOCKER_TLS_VERIFY=1 \
DOCKER_CERT_PATH=~/.docker/certs \
npm start
First, set up an SSH tunnel:
ssh -NL localhost:2375:/var/run/docker.sock user@remote-host
Then connect to the tunneled Docker:
DOCKER_HOST=tcp://localhost:2375 npm start
To integrate with VS Code and GitHub Copilot, add the following to your MCP settings file:
For Local Docker (~/.vscode/mcp-settings.json or in your workspace settings):
{
"mcpServers": {
"docker": {
"command": "node",
"args": ["/path/to/Docker-MCP/dist/index.js"]
}
}
}
For Remote Docker over TCP:
{
"mcpServers": {
"docker": {
"command": "node",
"args": ["/path/to/Docker-MCP/dist/index.js"],
"env": {
"DOCKER_HOST": "tcp://192.168.1.100:2375"
}
}
}
}
For Remote Docker with TLS:
{
"mcpServers": {
"docker": {
"command": "node",
"args": ["/path/to/Docker-MCP/dist/index.js"],
"env": {
"DOCKER_HOST": "https://192.168.1.100:2376",
"DOCKER_TLS_VERIFY": "1",
"DOCKER_CERT_PATH": "/home/user/.docker/certs"
}
}
}
}
For Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"docker": {
"command": "node",
"args": ["/path/to/Docker-MCP/dist/index.js"]
}
}
}
Alternative using npx (after publishing to npm):
{
"mcpServers": {
"docker": {
"command": "npx",
"args": ["@swartdraak/docker-mcp-server"]
}
}
}
Before using the MCP server, you can test your Docker connection with the included test utility:
# Test local Docker connection
node test-connection.js
# Test remote Docker via TCP
DOCKER_HOST=tcp://192.168.1.100:2375 node test-connection.js
# Test remote Docker via TLS
DOCKER_HOST=https://192.168.1.100:2376 \
DOCKER_TLS_VERIFY=1 \
DOCKER_CERT_PATH=~/.docker/certs \
node test-connection.js
# Test SSH tunnel connection
DOCKER_HOST=tcp://localhost:2375 node test-connection.js
The test utility will:
Once the MCP server is running, you can also use the validate_connection tool from your AI assistant:
"Validate my Docker connection"
This tool performs runtime connectivity tests and returns:
You can also test your connection directly with Docker CLI:
# Set environment variables
export DOCKER_HOST=tcp://192.168.1.100:2375
# Test commands
docker version
docker info
docker ps
For detailed setup instructions, troubleshooting, and platform-specific guides, see:
list_containersList all Docker containers (running or all)
{
"all": true
}
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.