Pare
Provides structured JSON output for Ansible commands, enabling agents to run playbooks and manage configuration and deployment tasks.
Provides structured JSON output for Bazel commands, enabling agents to build and test projects with Bazel.
Provides structured JSON output for Biome commands, enabling agents to lint and format code with Biome.
Provides structured JSON output for Bun commands, enabling agents to run, test, and manage Bun projects and packages.
Provides structured JSON output for CMake commands, enabling agents to configure and build C/C++ projects.
Provides structured JSON output for curl commands, enabling agents to make HTTP requests and interact with web APIs.
Provides structured JSON output for Deno commands, enabling agents to run, test, and manage Deno projects and dependencies.
Provides structured JSON output for Docker commands, enabling agents to build, run, and manage containers and images.
Provides structured JSON output for esbuild, enabling agents to bundle and build JavaScript/TypeScript projects.
Provides structured JSON output for ESLint, enabling agents to lint JavaScript and TypeScript code.
Provides structured JSON output for Git commands, enabling agents to manage repositories, inspect status, logs, diffs, and perform version control operations.
Provides structured JSON output for GitHub CLI (gh) commands, enabling agents to interact with repositories, issues, pull requests, and other GitHub features.
Provides structured JSON output for Gradle commands, enabling agents to build, test, and manage JVM projects with Gradle.
Provides structured JSON output for Helm commands, enabling agents to manage Kubernetes applications and charts.
Provides structured JSON output for Jest, enabling agents to run and interpret JavaScript tests.
Provides structured JSON output for MySQL commands, enabling agents to query and manage MySQL databases.
Provides structured JSON output for npm commands, enabling agents to install, manage, and inspect Node.js packages and dependencies.
Provides structured JSON output for Prettier, enabling agents to format code consistently.
Provides structured JSON output for pytest, enabling agents to run and interpret Python tests.
Provides structured JSON output for Python package management via pip, enabling agents to install, update, and inspect Python packages.
Provides structured JSON output for Redis commands, enabling agents to query and manage Redis data stores.
Provides structured JSON output for Ruby package management via gem, enabling agents to install, update, and inspect Ruby gems.
Provides structured JSON output for Cargo commands, enabling agents to build, test, and manage Rust packages and dependencies.
Provides structured JSON output for Swift commands, enabling agents to build, test, and manage Swift packages.
Provides structured JSON output for Terraform commands, enabling agents to plan, apply, and manage infrastructure as code.
Provides structured JSON output for Trivy, enabling agents to scan containers, filesystems, and repositories for vulnerabilities.
Provides structured JSON output for the TypeScript compiler (tsc), enabling agents to type-check and build TypeScript projects.
Provides structured JSON output for Vite, enabling agents to build and develop frontend projects with Vite.
Provides structured JSON output for Vitest, enabling agents to run and interpret JavaScript/TypeScript tests.
Provides structured JSON output for Webpack, enabling agents to bundle and build JavaScript projects.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pareshow me the current git branch, staged files, and unstaged changes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| 373 | 20 | 95% |
| 4,992 | 382 | 92% |
| 241 | 41 | 83% |
| 196 | 39 | 80% |
| 436 | 138 | 68% |
| 288 | 101 | 65% |
| 351 | 190 | 46% |
| 287 | 185 | 36% |
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.
Related MCP server: mcp-dev-servers
How It Works
Each Pare tool returns two outputs:
content— human-readable text, for MCP clients that display itstructuredContent— 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):
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.logPare 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.
Available Servers (28 packages, 240 tools)
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.
Category | Servers | Tools | Wraps |
Version Control | 55 | git, gh | |
Languages & Packages | npm, python, cargo, go, deno, bun, nix, dotnet, ruby, swift, jvm | 101 | npm, pip, cargo, go, deno, bun, nix, dotnet, gem, swift, gradle, maven |
Build, Lint & Test | 23 | tsc, esbuild, vite, webpack, eslint, prettier, biome, vitest, pytest, jest | |
Infrastructure | 40 | docker, kubectl, helm, terraform, ansible, trivy, ssh | |
Utilities | 21 | ripgrep, fd, curl, make, just, psql, mysql, redis, mongosh |
Tool Schemas — detailed response examples and field descriptions for every tool. See also Tool Response Examples for quick JSON samples.
Quick Setup
# 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 doctorAvailable presets: web, python, rust, go, jvm, dotnet, ruby, swift, mobile, devops, full
Setup Guides by Client
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
Configuration
Tool Selection
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/gitUniversal filter — restrict tools across all servers:
# Only register these specific tools across any server
PARE_TOOLS=git:status,git:log,npm:install npx @paretools/gitDisable all tools — set the env var to an empty string:
PARE_GIT_TOOLS= npx @paretools/git # no tools registeredEnv Var | Scope | Format | Example |
| All servers |
|
|
| One server |
|
|
Rules:
No env var = all tools enabled (default)
PARE_TOOLS(universal) takes precedence over per-server varsServer names use uppercase with hyphens replaced by underscores (e.g.,
PARE_MY_SERVER_TOOLS)Whitespace around commas is ignored
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:runIn 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"
}
}
}
}Troubleshooting
Issue | Solution |
| Use |
Slow first start | Run |
Node.js version error | Pare requires Node.js >= 20 |
NVM/fnm PATH issues | Use absolute path to |
MCP connection timeout | Set |
Too many tools filling context | Use tool selection env vars to limit tools, or only install the servers you need |
Contributing
Each server is a self-contained package. See CONTRIBUTING.md for the full guide.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
A registry of AI agent tools — MCP servers, APIs, CLIs, SDKs — kept current by automated ingestion.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceProvides MCP servers that wrap common developer tools (git, npm, docker, etc.) returning structured JSON output, enabling AI agents to reliably interact with these tools without parsing fragile terminal text.0139MIT
- AlicenseNot gradedqualityAmaintenanceProvides 7 MCP servers with 95 tools for git, GitHub, .NET, Ollama, Rust, template sync, and Python, enabling natural-language commands to perform real development operations.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides a deterministic set of 40 cross-platform command tools as an MCP server, replacing unsafe raw shell calls with structured JSON inputs and outputs for file system, process, network, and git operations.3 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides MCP servers that wrap common developer tools such as git, npm, Docker, Kubernetes, and test runners, returning schema-validated structured JSON instead of raw terminal text. This lets AI agents consume typed, token-efficient results directly without brittle string parsing or platform-dependent formatting issues.0MIT