start_container
Start a container
How to use it
start_container is exposed by the MCP Dockhand MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the start_container tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL MCP DOCKHAND LISTINGOther tools in MCP Dockhand (39)
Batch update containers
Check for image updates
Change file permissions
Create a new container
Create an empty file or directory in container (no content — use writecontainerfilecontent for that)
Create and optionally deploy a stack
Delete file in container
Delete a stack
Take down a stack (compose down)
Create a terminal exec session (execId + WS connectionInfo); does NOT run a one-shot command or return output — no such endpoint exists in the Dockhand API
Run a bulk lifecycle operation (start/stop/restart/remove/etc.) across containers, images, volumes, networks, or stacks
Get container details
Read file from container
Get container logs
List available shells
Get container disk sizes
Get resource usage stats
Get running processes
Get aggregated stats
Get pending updates
Get stack details
Read compose file
Read environment variables
Docker inspect (full details)
Browse files inside container
List all containers in an environment
List all stacks
Pause a container
Rename a container
Rename file in container
Restart a container
Restart a stack
Start a stack (compose up)
Stop a container
Stop a stack (compose stop)
Unpause a container
Update container settings
Update compose file
Update environment variables (merge by default — safe for partial updates; use mode="replace" to overwrite all)