mcp-server-docker

⚠ Stale — 106d ago

Provides an MCP (Model Context Protocol) server that exposes Docker Desktop container, network, image, and log management as MCP tools on Windows.

Evaluated Apr 04, 2026 (106d ago)
Repo ↗ Automation mcp docker developer-automation cli-integration container-management windows
⚙ Agent Friendliness
42
/ 100
Can an agent use this?
🔒 Security
24
/ 100
Is it safe for agents?
⚡ Reliability
18
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
70
Error Messages
0
Auth Simplicity
20
Rate Limits
0

🔒 Security

TLS Enforcement
10
Auth Strength
25
Scope Granularity
10
Dep. Hygiene
40
Secret Handling
40

The README explicitly recommends exposing Docker's daemon over TCP without TLS (tcp://localhost:2375 without TLS). No authentication/authorization for MCP tools is described, and no scope granularity is mentioned. Provided content also does not discuss secret handling practices, dependency scanning, or mitigation steps.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
0
Error Recovery
25
AF Security Reliability

Best When

You are running Docker Desktop on Windows with an MCP-capable client (e.g., Claude Desktop) and you want an agent to orchestrate Docker operations using predefined MCP tools.

Avoid When

You cannot or should not expose docker on tcp://localhost:2375 without TLS, or you need strong authentication, scoped permissions, and documented reliability/error-recovery semantics.

Use Cases

  • Automating Docker container lifecycle (create/start/stop/restart/remove) via an MCP-capable agent
  • Inspecting container, image, and network details from natural-language or tool-driven workflows
  • Managing Docker networks and connecting/disconnecting containers
  • Pulling/building/tagging/pushing/removing images programmatically
  • Retrieving container logs (optionally streaming) for debugging and monitoring

Not For

  • Environments where exposing the Docker daemon over TCP without TLS is not acceptable
  • Use cases requiring fine-grained, tenant-scoped authorization for Docker operations
  • Production setups needing documented SLAs, robust retry/idempotency guidance, and strict operational guarantees (based on provided README alone)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: No application-level auth described for the MCP server
OAuth: No Scopes: No

README instructs exposing Docker Desktop's daemon on tcp://localhost:2375 without TLS. No auth mechanism for the MCP server/tools is described in the provided content.

Pricing

Free tier: No
Requires CC: No

No pricing information is provided in the README content.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Requires Docker daemon exposure on tcp://localhost:2375 without TLS (security-sensitive).
  • Agent tools include destructive operations (e.g., remove_container, remove_image, stop/remove containers), so safety checks and confirmations may be needed.
  • Log retrieval supports streaming ('follow') which can cause long-running interactions if not bounded.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-docker.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
9228
Need Re-evaluation
Community Powered