Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y @paretools/[email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add io.github.dave-london-docker -- npx -y @paretools/docker@0.8.0टर्मिनल में चलाएँ।
{ "mcpServers": { "io.github.dave-london-docker": { "command": "npx", "args": [ "-y", "@paretools/[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्च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.
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:
Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like
eslintortsc, the main advantage is reliable structured data — agents can use typed JSON directly rather than parsing strings.
Each Pare tool returns two outputs:
content — human-readable text, for MCP clients that display itstructuredContent — typed, schema-validated JSON, ready for agents to processThis uses MCP's structuredContent and outputSchema features to provide type-safe, validated data that agents can rely on without custom parsing.
git statusRaw git output (~118 tokens):
On branch main
Your branch is ahead of 'origin/main' by 2 commits.
(use "git push" to publish your local commits)
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: src/index.ts
new file: src/utils.ts
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: README.md
Untracked files:
(use "git add <file>..." to include in what will be committed)
temp.log
Pare structured output (~59 tokens):
{
"branch": "main",
"upstream": "origin/main",
"ahead": 2,
"staged": [
{ "file": "src/index.ts", "status": "modified" },
{ "file": "src/utils.ts", "status": "added" }
],
"modified": ["README.md"],
"deleted": [],
"untracked": ["temp.log"],
"conflicts": [],
"clean": false
}
50% fewer tokens. Zero information lost. Fully typed. Savings scale with output verbosity — test runners and build logs see 80–92% reduction.
Install only the servers relevant to your stack — most projects need just 2–4. The full catalog covers a wide range of ecosystems so Pare works wherever you do.
Tool Schemas — detailed response examples and field descriptions for every tool. See also Tool Response Examples for quick JSON samples.
# 1. Configure MCP servers (non-interactive)
npx @paretools/init --client claude-code --preset web
# 2. Add agent rules to your project
# (append to existing CLAUDE.md, or copy if new)
cat node_modules/@paretools/init/rules/CLAUDE.md >> CLAUDE.md
# 3. Restart your client session
# 4. Validate
npx @paretools/init doctor
Available presets: web, python, rust, go, jvm, dotnet, ruby, swift, mobile, devops, full
Full Quickstart Guide — presets, ecosystem mapping, validation
Manual Configuration — config paths and formats for all clients
Agent Integration Guide — rule files, hooks, CLI-to-MCP mapping
By default, every Pare server registers all of its tools. If a server exposes tools you don't need — or you want to limit which tools are available to an agent — you can filter them with environment variables.
Per-server filter — restrict a single server's tools:
# Only register status and log in the git server
PARE_GIT_TOOLS=status,log npx @paretools/git
Universal filter — restrict tools across all servers:
# Only register these specific tools across any server
PARE_TOOLS=git:status,git:log,npm:install npx @paretools/git
Disable all tools — set the env var to an empty string:
PARE_GIT_TOOLS= npx @paretools/git # no tools registered
Rules:
PARE_TOOLS (universal) takes precedence over per-server varsPARE_MY_SERVER_TOOLS)Common patterns:
# Read-only git (no push, commit, add, checkout)
PARE_GIT_TOOLS=status,log,diff,branch,show
# Minimal npm
PARE_NPM_TOOLS=install,test,run
# Only specific tools across all servers
PARE_TOOLS=git:status,git:diff,npm:install,test:run
In JSON MCP config, set via the env key:
{
"mcpServers": {
"pare-git": {
"command": "npx",
"args": ["-y", "@paretools/git"],
"env": {
"PARE_GIT_TOOLS": "status,log,diff,show"
}
}
}
}
Each server is a self-contained package. See CONTRIBUTING.md for the full guide.
Structured Docker operations (ps, images, logs, build) as typed JSON.
{ "mcpServers": { "io.github.dave-london-docker": { "command": "npx", "args": [ "-y", "@paretools/[email protected]" ] } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Docker stdio पर लोकल चलता है।
पिछली जाँच 2026-11-09 को हुई। Structured Docker operations (ps, images, logs, build) as typed JSON.