Dev Tools & GitMCP RegistrynpmA · 88

pare-docker MCP server

Name: pare-docker
Author: Dave-London

io.github.Dave-London · Updated 8mo ago

Pare Docker ג€” Structured Docker operations (ps, images, logs, build, compose) as typed JSON.

At a glance

pare-docker is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y @paretools/docker`, and declares no required credentials. It scores A (88/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 139

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install pare-docker in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install pare-docker in Claude CodeAnthropic's agentic CLI

Add the server

bash

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

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install pare-docker in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

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

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install pare-docker in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

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

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install pare-docker in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.pare-docker]
command = "npx"
args = ["-y", "@paretools/docker"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install pare-docker in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

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

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install pare-docker in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

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

How to install pare-docker in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "pare-docker": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@paretools/docker"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does pare-docker expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 23 of 23 source files.

Nothing in this package's own source reaches for the filesystem, the network, or other programs.

How it was published

Published by a verified CI identity (github trusted publishing) rather than a personal token.
Has a provenance attestation tying this artifact to the commit it was built from.
1 npm maintainer — a single point of compromise · last published by GitHub Actions.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit 1 day ago — Actively maintained.
139 GitHub stars — Community adoption signal.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 88

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 1 day ago.
Adoption20%65%
139 stars.
Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
Provenance15%100%
Package and registry entry point at the same repository.
Packaging15%100%
Publishes a pinned version (0.8.1).

Documentation

Full README

  Pare

Reliable, structured CLI output for AI agents — no more parsing fragile terminal text.

Pare provides MCP servers that wrap common developer tools (git, npm, docker, test runners, etc.) and return clean, schema-validated JSON instead of raw terminal text. Agents get typed data they can act on directly, without brittle string parsing.

The Problem

Parsing CLI output is fragile. Raw terminal text includes ANSI escape codes, decorative headers, progress bars, locale-specific formatting, and platform differences that break agent workflows in subtle ways. An agent that works fine with git status on macOS may fail on Windows because the output format changed. A test runner's summary line might shift between versions, silently breaking a regex.

Pare eliminates this entire class of errors by returning schema-validated JSON with consistent field names, regardless of platform, tool version, or locale. As a bonus, structured output is significantly smaller — agents use fewer tokens per tool call:

| Tool Command | Raw Tokens | Pare Tokens | Reduction | | ----------------------------------------- | ---------: | ----------: | --------: | | docker build (multi-stage, 11 steps) | 373 | 20 | 95% | | git log --stat (5 commits, verbose) | 4,992 | 382 | 92% | | npm install (487 packages, warnings) | 241 | 41 | 83% | | vitest run (28 tests, all pass) | 196 | 39 | 80% | | cargo build (2 errors, help text) | 436 | 138 | 68% | | pip install (9 packages, progress bars) | 288 | 101 | 65% | | cargo test (12 tests, 2 failures) | 351 | 190 | 46% | | npm audit (4 vulnerabilities) | 287 | 185 | 36% |

Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like eslint or tsc, the main advantage is reliable structured data — agents can use typed JSON directly rather than parsing strings.

How It Works

Each Pare tool returns two outputs:

`content` — human-readable text, for MCP clients that display it
`structuredContent` — typed, schema-validated JSON, ready for agents to process

This uses MCP's structuredContent and outputSchema features to provide type-safe, validated data that agents can rely on without custom parsing.

Example: git status

Raw git output (~118 tokens):

Excerpt — the full document is on GitHub.

Alternatives to pare-docker

Maintain pare-docker? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![pare-docker on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-dave-london-pare-docker)](https://mcp-skills-hub.vercel.app/mcps/io-github-dave-london-pare-docker)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.