Returns typed JSON from Python tools like ruff, mypy, pip-audit and pip install so agents can act without parsing terminal text.
Also known as Dave-London/Pare, @paretools/python
- Stars
- 141
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.8.0
- Last commit
- Nov 10, 2026
- License
- MIT
What is Pare Python MCP?
Pare Python returns typed JSON from Python tools like ruff, mypy, pip-audit and pip install so agents can act without parsing terminal text.
Summary generated from the project's README
About Pare Python MCP server
Providing structured, schema-validated JSON for Python development tools is what this MCP server enables for AI agents. Instead of forcing an agent to parse fragile, human-readable terminal text that often includes ANSI escape codes or progress bars, this server returns typed data that can be acted upon directly. It is designed for developers using AI clients like Claude Desktop, Cursor, or Windsurf who need reliable tool outputs.
The server wraps specific Python utilities including ruff, mypy, pip-audit, and pip install. By converting these CLI commands into structuredContent, it significantly reduces token usage. For example, a pip install command can see a 65% reduction in tokens compared to raw terminal output. This makes it easier for agents to manage dependencies and code quality without the risk of breaking due to platform-specific formatting or version changes in the underlying tools.
What you can do with it
- 1Automated dependency managementAn agent can install new Python packages and immediately verify the installation using structured data.
- 2Code quality enforcementDevelopers can task an AI with running linting and type checking tools to ensure code standards are met.
Written from the project's README. Every use case is checked against a quote from it.
How to install Pare Python MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Pare Python MCP in Claude Code
$ claude mcp add python -- npx -y @paretools/pythonInstall Pare Python MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"python": {
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Install Pare Python MCP in VS Code
.vscode/mcp.json
{
"servers": {
"python": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Install Pare Python MCP in VS Code CLI
$ code --add-mcp '{"name":"python","type":"stdio","command":"npx","args":["-y","@paretools/python"]}'Install Pare Python MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"python": {
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Install Pare Python MCP in Codex
$ codex mcp add python -- npx -y @paretools/pythonInstall Pare Python MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.python] command = "npx" args = ["-y", "@paretools/python"]
Install Pare Python MCP in Gemini CLI
$ gemini mcp add -s user python npx -- -y @paretools/pythonInstall Pare Python MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"python": {
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Configuration
PARE_GIT_TOOLSPARE_NPM_TOOLSPARE_TOOLS
| Name | Description | |
|---|---|---|
| PARE_GIT_TOOLS | — | |
| PARE_NPM_TOOLS | — | |
| PARE_TOOLS | — |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubReliable, 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
eslintortsc, 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 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.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.
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 | git, github | 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 | build, lint, test, cmake, bazel | 23 | tsc, esbuild, vite, webpack, eslint, prettier, biome, vitest, pytest, jest |
| Infrastructure | docker, k8s, infra, security, remote | 40 | docker, kubectl, helm, terraform, ansible, trivy, ssh |
| Utilities | search, http, make, process, db | 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 doctor
Available presets: web, python, rust, go, jvm, dotnet, ruby, swift, mobile, devops, full
Setup Guides by Client
| Claude Code | Claude Desktop | Cursor |
| VS Code / Copilot | Windsurf | Cline / Roo Code |
| OpenAI Codex | Gemini CLI | Zed |
| Continue.dev |
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/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
| Env Var | Scope | Format | Example |
|---|---|---|---|
PARE_TOOLS |
All servers | server:tool,... |
git:status,npm:install |
PARE_{SERVER}_TOOLS |
One server | tool,... |
status,log,diff |
Rules:
- No env var = all tools enabled (default)
PARE_TOOLS(universal) takes precedence over per-server vars- Server 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: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"
}
}
}
}
Troubleshooting
| Issue | Solution |
|---|---|
npx not found / ENOENT on Windows |
Use cmd /c npx wrapper (see your client's setup guide) |
| Slow first start | Run npx -y @paretools/git once to cache, or install globally: npm i -g @paretools/git |
| Node.js version error | Pare requires Node.js >= 20 |
| NVM/fnm PATH issues | Use absolute path to npx: e.g., ~/.nvm/versions/node/v22/bin/npx |
| MCP connection timeout | Set MCP_TIMEOUT=30000 for Claude Code, or increase initTimeout in client config |
| 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
Pare Python MCP questions
How do I add Pare Python MCP to Claude Code?
Run claude mcp add python -- npx -y @paretools/python in your terminal. Add --scope user to make it available in every project.
How do I add Pare Python MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What Python tools does the Pare python server wrap?
It wraps ruff, mypy, pip-audit and pip install, returning structured JSON instead of raw terminal output.
Does Pare return structured JSON for python tools?
Yes, each tool returns human-readable content plus schema-validated structuredContent JSON.
How much smaller is Pare's output than raw CLI output?
In the README's example, pip install output dropped from 288 to 101 tokens, a 65% reduction.
Can I limit which tools a Pare server registers?
Yes, set PARE_TOOLS universally or PARE_{SERVER}_TOOLS for a single server to filter tools.