VERIFIED

Docker

Safety: 45/100

0.0(0)

Docker-mcp manages Docker containers and Compose stacks via Claude AI, offering container lifecycle management and log retrieval.

MCP ServersFreemium

Boost this tool

Subscribe to listing upgrades or segmented pushes.

Overview

Docker-mcp manages Docker containers and Compose stacks via Claude AI, offering container lifecycle management and log retrieval.

This MCP server provides useful Docker management capabilities but requires careful consideration due to its ability to create, deploy, and delete containers. It's relatively safe when used for monitoring and log retrieval, but risky when deploying complex Compose stacks or creating containers without proper resource constraints.

Performance is largely dependent on the Docker Engine and the complexity of the container operations. Large Compose stacks may take longer to deploy.

There are no direct monetary costs associated with this MCP server, but resource consumption (CPU, memory, disk) on the Docker host should be considered.

CloudPython448 starsMIT

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

ReadWriteExec

Client Compatibility

Claude Desktop

full

Cursor

untested

Windsurf

untested

VS Code (Copilot)

untested

Quickstart

Install

npx @smithery/cli install docker-mcp --client claude

Claude Desktop Config

{
  "mcpServers": {
    "docker-mcp": {
      "command": "uvx",
      "args": [
        "docker-mcp"
      ]
    }
  }
}

Tools (4)

moderate

create-container

Creates a Docker container with specified image, name, ports, and environment variables.

Can create containers with potentially insecure configurations.

high

deploy-compose

Deploys a Docker Compose stack using a provided YAML file.

Compose files can contain arbitrary configurations, posing significant security risks.

safe

get-logs

Retrieves logs from a specified Docker container.

Read-only operation with no side effects.

safe

list-containers

Lists all Docker containers and their status.

Read-only operation with no side effects.

Security

Auth Method

None

Data Locality

cloud

Known Risks

!Unvalidated compose files could lead to container deployment failures or security vulnerabilities.
!Lack of resource limits on container creation can lead to resource exhaustion on the Docker host.
!Incorrect container configurations can expose services unintentionally.
!Absence of network management tools can lead to network conflicts.

Safety Score

moderate risk

Positive

+Requires local Docker Engine, limiting external exposure.
+Tool-based access control limits the scope of operations.
+Clear tool definitions with specific parameters.
+No direct internet access from the MCP server itself.

Risks

-Can create, deploy, and delete containers, posing a risk of unintended consequences.
-No built-in sandboxing; relies on Docker's container isolation.
-Lack of resource limits can lead to resource exhaustion.
-Compose deployments can introduce complex configurations with potential vulnerabilities.

Use Cases

Container Management

-Creating development containers for testing.
-Deploying simple applications using Docker Compose.
-Managing container lifecycles (start, stop, remove).

Log Analysis

-Troubleshooting application errors by retrieving container logs.
-Monitoring container activity for debugging purposes.
-Analyzing logs for performance bottlenecks.

Infrastructure Automation

-Automating container deployment as part of a CI/CD pipeline.
-Orchestrating multi-container applications with Docker Compose.
-Simplifying container management tasks for developers.

Who Is This For?

Best For

Developers needing to manage Docker containers locally.
Teams using Docker Compose for application deployment.
Automating simple container management tasks.
Quickly deploying and testing containerized applications.

Not Ideal For

Managing large-scale, production Docker environments.
Environments requiring strict security controls and auditing.
Complex container orchestration scenarios beyond Docker Compose.
Situations where resource limits and isolation are critical.

Autonomy & Execution

Default ModeRead and Write enabled

Destructive Tools

The server allows for full read/write access to Docker, so caution is advised when granting autonomy. There is no built-in sandboxing or rollback support.

StatelessYes

Retry LogicNot documented

ConcurrencySingle-threaded

Production Tip

Implement robust validation of Docker Compose files and container configurations before deployment to prevent errors in production.

FAQ

What Docker version is required?

Docker Desktop or Docker Engine is required, but the specific version compatibility isn't documented.

How do I configure resource limits for containers?

Resource limits are not directly supported by this MCP server. You need to configure them within the Docker Compose file or using Docker CLI options.

Does this support Docker Swarm or Kubernetes?

No, this MCP server is designed for standalone Docker containers and Docker Compose stacks, not for Swarm or Kubernetes orchestration.

Can I use environment variables in my Docker Compose files?

Yes, you can use environment variables in your Docker Compose files, but the MCP server itself doesn't provide built-in environment variable management.

How do I handle errors during Docker Compose deployment?

The MCP server will likely propagate errors from Docker Compose. Check the container logs and Docker Engine logs for details.

Is there a way to rollback a failed Docker Compose deployment?

No, there is no built-in rollback support. You need to manually revert the changes or use a separate version control system for your Compose files.

How do I update an existing Docker Compose stack?

You can update an existing stack by modifying the Compose file and redeploying it using the `deploy-compose` tool.

Team

1-10

Alex Andru

Core Contributor

Ali Sadykov

Core Contributor

Metrics

Discovered2/14/2026

Reviews0

Saved By0 users

Related Tools

Docker - AI Tool Review & Alternatives | Flaex AI