← Back to directory
P

Pare Docker

Community
Structured Docker operations for agents, as typed JSON.
Category
Dev Tools #416 of 438
Stars
★ 138 Popular
Transport
stdio (local process)
Runtime
Node.js >= 20 · Docker
Credentials
No credential needed
License
MIT
Last commit
Tools
5
29FMRS · D

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.

Strongest · Setup experience 7/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
5/20
Maintenance
6/20
Documentation
6/20
Setup experience
7/20
Why each score
Reliability 5/20
The manifest is well-formed and superficially consistent (name, npm package, version, stdio transport), and the README claims structured JSON output for Docker tools. However, no source code, tests, or CI workflow for this specific server was provided, so startup, MCP handshake, and actual tool behavior cannot be verified. Under the static review rules, missing evidence is a deduction; the score stays well below 12.
Security and permissions 5/20
No red-line issues (malware, credential theft, exfiltration, unconfirmed destructive defaults) are visible in the supplied material. Yet there is no source or config showing credential handling, least privilege, confirmation for side-effectful Docker operations (build, compose, images), or data-flow disclosure. The documented tool-filtering env vars reduce exposure but are not a substitute for built-in confirmation, so the score is low.
Maintenance 6/20
The repository declares an MIT license, version 0.22.0, and CI/OpenSSF badges, and is not archived. These are repository-level signals from untrusted README/manifest evidence; there is no commit history, release notes, dependency-update evidence, or security-response channel tied to the Docker server. Sustained maintenance cannot be confirmed.
Documentation 6/20
The README provides general installation, tool-selection env vars, troubleshooting, and a git MCP config example, which are useful. But Docker-specific tool parameters, response schemas, auth/limits are only linked and not supplied; the examples are for git/npm rather than Docker, so the documentation for this server is incomplete.
Setup experience 7/20
Generic setup via npx @paretools/init and client config examples exist, and the Docker package identifier plus stdio transport make a straightforward npx-based configuration plausible. However, no Docker-specific config example or verifiable execution evidence was provided; per the static cap of 15 and the uncertainty involved, the score is modest.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or codeUses the network

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.

Setup

Before you start

Runtime:Node.js >= 20 · Docker

Other optional settings (1)
PARE_TOOLS optional Universal tool filter in server:tool form (e.g. docker:ps) that limits tools registered across all servers; not required.
  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"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "pare-docker": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add pare-docker -- npx -y @paretools/docker

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

After connecting, the pare-docker server should register tools such as docker ps, docker images, docker logs, docker build, and docker compose in the client's tool list; asking it to list running containers confirms the connection works.

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.

Things to try

Once connected, you can ask your AI assistant things like:

  • List the currently running Docker containers
  • Show the recent logs for container my-app
  • Build the Docker image for this project and report the result
  • Start the local service stack with docker compose

Tools 5

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

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 Desktop
Claude Code
Cursor
VS Code
Windsurf
Cline
Roo Code
Codex
Gemini CLI
Zed
Continue

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method