← Back to directory
P

Pare Docker

Community
Structured Docker operations for agents, as typed JSON.
GitHub source repository ↗
★ 138 Stars Category · Dev Tools Popular Source revision 57e1980e8375
29FMRS · D
Reliability
5/20
Security and permissions
5/20
Maintenance
6/20
Documentation
6/20
Setup experience
7/20

Pare Docker is part of the Pare suite, focusing on providing structured Docker operations for AI agents. It significantly reduces token consumption by returning schema-validated JSON and eliminates the fragility of parsing terminal text. Suitable for developers wanting to integrate reliable Docker automation into their workflows, but requires Node.js environment and MCP client configuration.

Read the FMRS scoring method →

Pare Docker is an MCP server that wraps Docker command-line tools and returns structured, typed JSON output. It provides tools for container listing, image listing, logs, build, and compose operations, all returning schema-validated JSON to avoid brittle text parsing, improving agent reliability and token efficiency.

Tools

docker ps
List containers, returning typed JSON.
docker images
List images, returning typed JSON.
docker logs
Fetch container logs, returning typed JSON.
docker build
Build an image, returning typed JSON.
docker compose
Run Docker Compose operations, returning typed JSON.

Setup

  1. Ensure Node.js >= 20 is installed. 2. Add the following JSON to your MCP client configuration: {"mcpServers":{"pare-docker":{"command":"npx","args":["-y","@paretools/docker"]}}}. 3. Restart your client.

First run via npx may be slow; run npx -y @paretools/docker once to cache, or install globally with npm i -g @paretools/docker.

claude_desktop_config.json
{
  "mcpServers": {
    "pare-docker": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}

Fit and risk

Best for

  • Users of AI coding tools (Claude, Cursor, etc.) who want to reduce token usage.
  • Agents that need reliable, unambiguous Docker output for automated decision-making.
  • Developers using Docker as part of their infrastructure and wanting MCP integration in their workflow.

Not for

  • Users requiring interactive terminal control or full Docker CLI features (like attach, exec -it).
  • Users unfamiliar with MCP configuration or Node.js environments.
  • Users needing raw output from the Docker daemon, not structured data.

Required permissions

  • Permissions to execute Docker commands, such as access to Docker socket or daemon (depending on environment).
  • Network access for npx to download npm packages or Docker images (if pulling during builds).
  • Filesystem access to read Dockerfiles or build contexts (if applicable).

Risks and side effects

  • Running Docker commands may affect containers, images, or builds, e.g., removing containers or modifying images.
  • Misconfiguration or network issues can cause Docker commands to fail, and agents may receive incomplete structured data.
  • Using npx may introduce supply-chain risks, as remote code is downloaded and executed on each invocation.

Troubleshooting

  1. Check Node.js version: Ensure >= 20 (`node -v`).
  2. If npx is not found or ENOENT on Windows, use `cmd /c npx` wrapper.
  3. If MCP connection times out, set env var `MCP_TIMEOUT=30000` or increase initTimeout in client config.
  4. Verify Docker daemon is running and that the current user has permissions to access the Docker socket.
  5. Try running `npx -y @paretools/docker` to verify the server starts correctly.

Use cases

AI agents need to retrieve Docker container status, image info, or logs in a structured way for automation.
In CI/CD pipelines, agents need to parse Docker build output for error detection or summarization.
Managing multi-container environments with compose files, where agents need typed results for orchestration.

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS CodeFull support
WindsurfFull support
ClineFull support
Roo CodeFull support
OpenAI CodexFull support
Gemini CLIFull support
ZedFull support
Continue.devFull support