Connections & Capabilities
Connects To
Capabilities
Exposed MCP Tools (19)
list_containersLists all containers.
Read-only operation.
create_containerCreates a new container.
Can create containers with unintended configurations.
run_containerRuns a container.
Can run containers with unintended configurations.
recreate_containerRecreates an existing container.
Can modify existing containers.
start_containerStarts a stopped container.
Starting a container can have side effects.
fetch_container_logsFetches logs from a container.
Read-only operation.
stop_containerStops a running container.
Stopping a container can interrupt services.
remove_containerRemoves a container.
Destructive operation.
list_imagesLists all images.
Read-only operation.
pull_imagePulls an image from a registry.
Pulling an image can introduce new software.
push_imagePushes an image to a registry.
Pushing an image can expose internal software.
build_imageBuilds a new image from a Dockerfile.
Building an image can execute arbitrary code.
remove_imageRemoves an image.
Destructive operation.
list_networksLists all networks.
Read-only operation.
create_networkCreates a new network.
Creating a network can affect container connectivity.
remove_networkRemoves a network.
Destructive operation.
list_volumesLists all volumes.
Read-only operation.
create_volumeCreates a new volume.
Creating a volume can consume disk space.
remove_volumeRemoves a volume.
Destructive operation.
Safety Assessment
This MCP server provides a convenient way to manage Docker resources using natural language, but it carries significant risks. It's relatively safe for read-only operations and inspecting existing resources. However, using it to create or modify containers without careful review is risky, as the LLM could introduce unintended configurations or security vulnerabilities.
- Doesn't support sensitive Docker options like `--privileged` or `--cap-add/--cap-drop` by default.
- Requires user to review containers created by the LLM.
- Provides tools for listing and inspecting existing Docker resources.
- Allows connecting to remote Docker daemons over SSH.
- Exposes Docker daemon control, potentially impacting the host machine.
- Doesn't inherently sandbox containers created by the LLM.
- Warns against configuring containers with sensitive data due to LLM interaction.
- Relies on Docker's security model, which isn't a secure sandbox.
- LLM can create and manage containers, networks, and volumes.