Pare Python

io.github.Dave-LondonPublished by GitHub account Dave-Londonv0.8.1Updated Oct 24, 2026

Pare Python ג€” Structured Python tool output (ruff, mypy, pip, uv, black, pytest) as typed JSON.

VerifiedSTDIODesktop onlyDeveloper Tools Data & Analytics

Server details

Identifier: io.github.Dave-London/pare-python
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Dave-London for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Dave-London%2Fpare-python.svg)](https://sourceweft.com/mcp/io.github.Dave-London%2Fpare-python?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Wraps Python tooling (ruff, mypy, pip, uv, black, pytest) so an assistant gets schema-validated JSON instead of raw terminal text.

What you can do: Pare Python is one package in the Pare family of MCP servers that wrap command-line developer tools and return structured output. Each tool returns human-readable content plus typed, schema-validated structuredContent, so results such as lint findings, type errors, dependency installs and test results arrive as consistent fields rather than ANSI-decorated text. The README states the family covers 28 packages and 240 tools across version control, languages and packages, build/lint/test, infrastructure and utilities, with this package covering the Python ecosystem.
When to use it: Use it when an assistant needs to run Python linting, type checking, dependency management or tests and act on the results programmatically. It is most valuable for verbose commands such as installs and test runs, where the README reports large token reductions, and for workflows that must behave the same across platforms and tool versions.
Requirements: Runs locally over stdio as an npm package (@paretools/python) started with npx, so Node.js 20 or higher is required. The wrapped Python tools (ruff, mypy, pip, uv, black, pytest) must be available on the machine. No authentication, environment variables or headers are declared; tool filtering is optional via PARE_TOOLS or PARE_{SERVER}_TOOLS.

Before you install

The server executes local developer commands, so tools that install packages, modify files or run tests act on the user's machine and project. Tool selection variables such as PARE_TOOLS and PARE_{SERVER}_TOOLS can restrict which commands are exposed, for example to read-only operations. No credentials are requested by this package.

Installation

In SourceWeft

Open Pare Python in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Image] Pare

[CI] [codecov] [npm] [Downloads] [TypeScript] [License: MIT] [Node.js >= 20] [OpenSSF Scorecard] [OpenSSF Best Practices]

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):

On branch mainYour 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

On branch mainYour 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):

json

{  "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}

{  "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

bash

# 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. Validatenpx @paretools/init doctor

# 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. Validatenpx @paretools/init doctor

Available 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:

Universal filter — restrict tools across all servers:

bash

# Only register these specific tools across any serverPARE_TOOLS=git:status,git:log,npm:install npx @paretools/git

# Only register these specific tools across any serverPARE_TOOLS=git:status,git:log,npm:install npx @paretools/git

Disable all tools — set the env var to an empty string:

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:

bash

# Read-only git (no push, commit, add, checkout)PARE_GIT_TOOLS=status,log,diff,branch,show
# Minimal npmPARE_NPM_TOOLS=install,test,run
# Only specific tools across all serversPARE_TOOLS=git:status,git:diff,npm:install,test:run

# Read-only git (no push, commit, add, checkout)PARE_GIT_TOOLS=status,log,diff,branch,show
# Minimal npmPARE_NPM_TOOLS=install,test,run
# Only specific tools across all serversPARE_TOOLS=git:status,git:diff,npm:install,test:run

In JSON MCP config, set via the env key:

json

{  "mcpServers": {    "pare-git": {      "command": "npx",      "args": ["-y", "@paretools/git"],      "env": {        "PARE_GIT_TOOLS": "status,log,diff,show"      }    }  }}

{  "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

MIT

Source: README.md at commit 57e1980

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.8.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts


Claude Code	Claude Desktop	Cursor
VS Code / Copilot	Windsurf	Cline / Roo Code
OpenAI Codex	Gemini CLI	Zed
Continue.dev

Env Var	Scope	Format	Example
`PARE_TOOLS`	All servers	`server:tool,...`	`git:status,npm:install`
`PARE_{SERVER}_TOOLS`	One server	`tool,...`	`status,log,diff`

Pare Python

Overview

Installation

In SourceWeft

Other MCP clients

README

[Image] Pare

The Problem

How It Works

Example: git status

Available Servers (28 packages, 240 tools)

Quick Setup

Setup Guides by Client

Configuration

Tool Selection

Troubleshooting

Contributing

License

Tools

Version history

Score

Example: `git status`