Menghasilkan JSON terstruktur yang telah divalidasi skemanya untuk Python CLI tools seperti ruff, mypy, pip, uv, black, dan pytest.
Juga dikenal sebagai Dave-London/Pare, @paretools/python
- Stars
- 141
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.8.1
- Commit terakhir
- 10 Nov 2026
- Lisensi
- MIT
Apa itu Pare Python MCP?
Menghasilkan JSON terstruktur yang telah divalidasi skemanya untuk Python CLI tools seperti ruff, mypy, pip, uv, black, dan pytest.
Ringkasan dibuat dari README proyek
Tentang Pare Python MCP server
Pare-python memungkinkan AI agent untuk mendapatkan JSON terstruktur yang telah divalidasi skemanya untuk berbagai Python development tools. Alih-alih memaksa agent untuk memproses teks terminal yang rapuh karena mengandung ANSI escape codes atau format spesifik platform, server ini mengonversi output dari CLI tools menjadi data bertipe. Hal ini memungkinkan developer menggunakan AI client seperti Claude Desktop, Cursor, atau Windsurf untuk berinteraksi dengan lingkungan Python mereka dengan reliabilitas yang jauh lebih tinggi.
Server ini membungkus perintah umum seperti ruff, mypy, pip, uv, black, dan pytest. Dengan mengembalikan structuredContent alih-alih string mentah, server ini secara signifikan mengurangi penggunaan token, sering kali lebih dari 60% untuk perintah verbose seperti pip install. Anda dapat mengonfigurasi tools spesifik mana yang diekspos ke agent menggunakan environment variables seperti PARE_PYTHON_TOOLS untuk menjaga toolset tetap minimal dan fokus. Setup ini sangat ideal bagi developer yang ingin asisten coding AI mereka melakukan linting, type checking, dan dependency management tanpa risiko pola regex yang rusak atau error saat parsing.
Apa yang bisa Anda lakukan dengannya
- 1Manajemen dependency otomatisAI agent dapat menginstal Python packages menggunakan pip dan menerima daftar item yang terinstal secara terstruktur, bukan sekadar tumpukan teks.
- 2Linting dan formatting kode yang reliabelDeveloper dapat menugaskan agent untuk menjalankan ruff atau black guna memastikan kualitas kode melalui feedback JSON bertipe.
- 3Eksekusi dan analisis pengujian otomatisAgent dapat menjalankan pytest dan langsung memahami hasil pengujian melalui data yang telah divalidasi skemanya.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Pare Python MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Pare Python MCP di Claude Code
$ claude mcp add pare-python -- npx -y @paretools/pythonInstal Pare Python MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pare-python": {
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Instal Pare Python MCP di VS Code
.vscode/mcp.json
{
"servers": {
"pare-python": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Instal Pare Python MCP di VS Code CLI
$ code --add-mcp '{"name":"pare-python","type":"stdio","command":"npx","args":["-y","@paretools/python"]}'Instal Pare Python MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pare-python": {
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Instal Pare Python MCP di Codex
$ codex mcp add pare-python -- npx -y @paretools/pythonInstal Pare Python MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.pare-python] command = "npx" args = ["-y", "@paretools/python"]
Instal Pare Python MCP di Gemini CLI
$ gemini mcp add -s user pare-python npx -- -y @paretools/pythonInstal Pare Python MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pare-python": {
"command": "npx",
"args": [
"-y",
"@paretools/python"
]
}
}
}Konfigurasi
PARE_GIT_TOOLSPARE_NPM_TOOLSPARE_TOOLS
| Nama | Deskripsi | Tipe |
|---|---|---|
| PARE_GIT_TOOLS | — | |
| PARE_NPM_TOOLS | — | |
| PARE_TOOLS | — |
Pengecekan otomatis
Berjalan 12 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di 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
Pertanyaan tentang Pare Python MCP
Bagaimana cara menambahkan Pare Python MCP ke Claude Code?
Jalankan claude mcp add pare-python -- npx -y @paretools/python di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Pare Python MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apa yang dikembalikan oleh Pare Python sebagai pengganti output terminal mentah?
Pare mengembalikan JSON bersih yang telah divalidasi skemanya dengan nama field yang konsisten untuk Python tools seperti ruff, mypy, pip, uv, black, dan pytest.
Python tools mana saja yang dibungkus oleh Pare?
Pare Python server membungkus pip di antara tools bahasa dan package, serta pytest dalam tooling pengujiannya.
Apakah tools Pare menyediakan output yang dapat dibaca manusia sekaligus output bertipe (typed)?
Ya, setiap tool mengembalikan teks yang dapat dibaca manusia di bagian content dan JSON bertipe yang telah divalidasi skemanya di bagian structuredContent.
Dapatkah saya membatasi tools mana yang didaftarkan oleh Pare server?
Ya, gunakan environment variables per-server seperti PARE_PYTHON_TOOLS untuk mendaftarkan hanya tools pilihan Anda.
Apakah Pare mengurangi penggunaan token untuk perintah yang verbose?
Ya, output terstruktur lebih kecil dibandingkan teks terminal mentah, dengan pengurangan signifikan pada output install dan build yang verbose.