
Docker Management
- 1 installs
- 2 repo stars
- Updated March 10, 2026
- ofershap/mcp-server-docker
Manages Docker containers and images over MCP: list, start, stop, restart, remove, exec commands, read logs, and inspect live stats.
About
This skill exposes MCP tools to control Docker containers and images, run commands inside containers, tail logs, and read CPU/memory/network stats. A developer uses it to inspect and debug running containers.
- 10 tools for container and image lifecycle
- container_stats and container_logs for debugging
Docker Management by the numbers
- 1 all-time installs (skills.sh)
- Ranked #933 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ofershap/mcp-server-docker --skill docker-managementAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 2 |
| Last updated | March 10, 2026 |
| Repository | ofershap/mcp-server-docker ↗ |
What it does
Manages Docker containers and images over MCP: list, start, stop, restart, remove, exec commands, read logs, and inspect live stats.
Files
Docker Management via MCP
Use this skill when you need to manage Docker containers, inspect logs, run commands inside containers, or check resource usage.
Available Tools
| Tool | What it does |
|---|---|
list_containers | List running (or all) containers with status, ports, image |
container_logs | Get recent logs from a container |
start_container | Start a stopped container |
stop_container | Stop a running container |
restart_container | Restart a container |
remove_container | Remove a container (optional force) |
exec_command | Execute a command inside a running container |
container_stats | Get live CPU, memory, and network stats |
list_images | List all Docker images on the host |
remove_image | Remove a Docker image |
Workflow
1. Start with list_containers to see what's running 2. Use container names or IDs from the list for all other operations 3. For debugging: container_logs first, then exec_command to investigate 4. Use container_stats to check resource usage when diagnosing performance issues
Key Patterns
list_containersshows only running containers by default — passall: truefor stopped ones toocontainer_logsreturns the last N lines — passtailto control how manyexec_commandruns inside a running container — the container must be started firstremove_containerwithforce: truestops and removes in one step
Safety
- Always confirm before stopping or removing containers
- Never remove containers in production without explicit user approval
- Check
container_statsbefore restarting to understand if the issue is resource-related