Skip to content
Back to search

Pare

Dev tools, optimized for agents. Structured, token-efficient MCP servers for git, test runners, npm, Docker, and more.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Dave-London/Pare with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Dave-London/Pare'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dave-london--pare/badge.svg)](/listings/dave-london--pare)

HTML

<a href="/listings/dave-london--pare"><img src="/api/listings/dave-london--pare/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

# 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](./docs/setup/claude-code.md) | [Claude Desktop](./docs/setup/claude-desktop.md) | [Cursor](./docs/setup/cursor.md) | | [VS Code / Copilot](./docs/setup/vscode.md) | [Windsurf](./docs/setup/windsurf.md) | [Cline / Roo Code](./docs/setup/cline.md) | | [OpenAI Codex](./docs/setup/codex.md) | [Gemini CLI](./docs/setup/gemini-cli.md) | [Zed](./docs/setup/zed.md) | | [Continue.dev](./docs/setup/continue-dev.md) | | |

> **[Full Quickstart Guide](./docs/quickstart.md)** — presets, ecosystem mapping, validation > > **[Manual Configuration](./docs/manual-configuration.md)** — config paths and formats for all clients > > **[Agent Integration Guide](./docs/agent-integration.md)** — rule files, hooks, CLI-to-MCP mapping

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 222 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h1><img src="assets/logo.png" alt="" width="80" valign="middle" />&nbsp;&nbsp;Pare</h1>
  2. [![CI](https://github.com/Dave-London/Pare/actions/workflows/ci.yml/badge.svg)](https://github.com/Dave-London/Pare/actions/workflows/ci.yml)
  3. [![codecov](https://codecov.io/gh/Dave-London/Pare/graph/badge.svg)](https://codecov.io/gh/Dave-London/Pare)
  4. [![npm](https://img.shields.io/npm/v/@paretools/git.svg?label=npm)](https://www.npmjs.com/package/@paretools/git)
  5. [![Downloads](https://img.shields.io/npm/dm/@paretools/git.svg)](https://www.npmjs.com/package/@paretools/git)
  6. [![TypeScript](https://img.shields.io/badge/TypeScript-strict-blue.svg)](https://www.typescriptlang.org/)
  7. [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/Dave-London/Pare/blob/main/LICENSE)
  8. [![Node.js >= 20](https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg)](https://nodejs.org)
  9. [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/Dave-London/Pare/badge)](https://scorecard.dev/viewer/?uri=github.com/Dave-London/Pare)
  10. [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/11962/badge)](https://www.bestpractices.dev/projects/11962)
  11. **Reliable, structured CLI output for AI agents — no more parsing fragile terminal text.**
  12. Pare provides [MCP](https://modelcontextprotocol.io) 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.
  13. ## The Problem
  14. 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.
  15. 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:
  16. | Tool Command | Raw Tokens | Pare Tokens | Reduction |
  17. | ----------------------------------------- | ---------: | ----------: | --------: |
  18. | `docker build` (multi-stage, 11 steps) | 373 | 20 | **95%** |
  19. | `git log --stat` (5 commits, verbose) | 4,992 | 382 | **92%** |
  20. | `npm install` (487 packages, warnings) | 241 | 41 | **83%** |
  21. | `vitest run` (28 tests, all pass) | 196 | 39 | **80%** |
  22. | `cargo build` (2 errors, help text) | 436 | 138 | **68%** |
  23. | `pip install` (9 packages, progress bars) | 288 | 101 | **65%** |
  24. | `cargo test` (12 tests, 2 failures) | 351 | 190 | **46%** |
  25. | `npm audit` (4 vulnerabilities) | 287 | 185 | **36%** |
  26. > 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.
  27. ## How It Works
  28. Each Pare tool returns two outputs:
  29. - **`content`** — human-readable text, for MCP clients that display it
  30. - **`structuredContent`** — typed, schema-validated JSON, ready for agents to process
  31. This uses MCP's `structuredContent` and `outputSchema` features to provide type-safe, validated data that agents can rely on without custom parsing.
  32. ## Example: `git status`
  33. **Raw git output (~118 tokens):**
  34. ```
  35. On branch main
  36. Your branch is ahead of 'origin/main' by 2 commits.
  37. (use "git push" to publish your local commits)
  38. Changes to be committed:
  39. (use "git restore --staged <file>..." to unstage)
  40. modified: src/index.ts
  41. new file: src/utils.ts
  42. Changes not staged for commit:
  43. (use "git add <file>..." to update what will be committed)
  44. (use "git restore <file>..." to discard changes in working directory)
  45. modified: README.md
  46. Untracked files:
  47. (use "git add <file>..." to include in what will be committed)
  48. temp.log
  49. ```
  50. **Pare structured output (~59 tokens):**
  51. ```json
  52. {
  53. "branch": "main",
  54. "upstream": "origin/main",
  55. "ahead": 2,
  56. "staged": [
  57. { "file": "src/index.ts", "status": "modified" },
  58. { "file": "src/utils.ts", "status": "added" }
  59. ],
  60. "modified": ["README.md"],
  61. "deleted": [],
  62. "untracked": ["temp.log"],
  63. "conflicts": [],
  64. "clean": false
  65. }
  66. ```
  67. 50% fewer tokens. Zero information lost. Fully typed. Savings scale with output verbosity — test runners and build logs see 80–92% reduction.
  68. ## Available Servers (28 packages, 240 tools)
  69. 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.
  70. | Category | Servers | Tools | Wraps |
  71. | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----: | -------------------------------------------------------------------------- |
  72. | Version Control | [git](./packages/server-git), [github](./packages/server-github) | 55 | git, gh |
  73. | Languages & Packages | [npm](./packages/server-npm), [python](./packages/server-python), [cargo](./packages/server-cargo), [go](./packages/server-go), [deno](./packages/server-deno), [bun](./packages/server-bun), [nix](./packages/server-nix), [dotnet](./packages/server-dotnet), [ruby](./packages/server-ruby), [swift](./packages/server-swift), [jvm](./packages/server-jvm) | 101 | npm, pip, cargo, go, deno, bun, nix, dotnet, gem, swift, gradle, maven |
  74. | Build, Lint & Test | [build](./packages/server-build), [lint](./packages/server-lint), [test](./packages/server-test), [cmake](./packages/server-cmake), [bazel](./packages/server-bazel) | 23 | tsc, esbuild, vite, webpack, eslint, prettier, biome, vitest, pytest, jest |
  75. | Infrastructure | [docker](./packages/server-docker), [k8s](./packages/server-k8s), [infra](./packages/server-infra), [security](./packages/server-security), [remote](./packages/server-remote) | 40 | docker, kubectl, helm, terraform, ansible, trivy, ssh |
  76. | Utilities | [search](./packages/server-search), [http](./packages/server-http), [make](./packages/server-make), [process](./packages/server-process), [db](./packages/server-db) | 21 | ripgrep, fd, curl, make, just, psql, mysql, redis, mongosh |
  77. > **[Tool Schemas](./docs/tool-schemas/)** — detailed response examples and field descriptions for every tool.
  78. > See also **[Tool Response Examples](./docs/tool-response-examples.md)** for quick JSON samples.
  79. ## Quick Setup
  80. ```bash
  81. # 1. Configure MCP servers (non-interactive)
  82. npx @paretools/init --client claude-code --preset web
  83. # 2. Add agent rules to your project
  84. # (append to existing CLAUDE.md, or copy if new)
  85. cat node_modules/@paretools/init/rules/CLAUDE.md >> CLAUDE.md
  86. # 3. Restart your client session
  87. # 4. Validate
  88. npx @paretools/init doctor
  89. ```
  90. **Available presets:** `web`, `python`, `rust`, `go`, `jvm`, `dotnet`, `ruby`, `swift`, `mobile`, `devops`, `full`
  91. ### Setup Guides by Client
  92. | | | |
  93. | -------------------------------------------- | ------------------------------------------------ | ----------------------------------------- |
  94. | [Claude Code](./docs/setup/claude-code.md) | [Claude Desktop](./docs/setup/claude-desktop.md) | [Cursor](./docs/setup/cursor.md) |
  95. | [VS Code / Copilot](./docs/setup/vscode.md) | [Windsurf](./docs/setup/windsurf.md) | [Cline / Roo Code](./docs/setup/cline.md) |
  96. | [OpenAI Codex](./docs/setup/codex.md) | [Gemini CLI](./docs/setup/gemini-cli.md) | [Zed](./docs/setup/zed.md) |
  97. | [Continue.dev](./docs/setup/continue-dev.md) | | |
  98. > **[Full Quickstart Guide](./docs/quickstart.md)** — presets, ecosystem mapping, validation
  99. >
  100. > **[Manual Configuration](./docs/manual-configuration.md)** — config paths and formats for all clients
  101. >
  102. > **[Agent Integration Guide](./docs/agent-integration.md)** — rule files, hooks, CLI-to-MCP mapping
  103. ## Configuration
  104. ### Tool Selection
  105. 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.
  106. **Per-server filter** — restrict a single server's tools:
  107. ```bash
  108. # Only register status and log in the git server
  109. PARE_GIT_TOOLS=status,log npx @paretools/git
  110. ```
  111. **Universal filter** — restrict tools across all servers:
  112. ```bash
  113. # Only register these specific tools across any server
  114. PARE_TOOLS=git:status,git:log,npm:install npx @paretools/git
  115. ```
  116. **Disable all tools** — set the env var to an empty string:
  117. ```bash
  118. PARE_GIT_TOOLS= npx @paretools/git # no tools registered
  119. ```
  120. | Env Var | Scope | Format | Example |
  121. | --------------------- | ----------- | ----------------- | ------------------------ |
  122. | `PARE_TOOLS` | All servers | `server:tool,...` | `git:status,npm:install` |
  123. | `PARE_{SERVER}_TOOLS` | One server | `tool,...` | `status,log,diff` |
  124. **Rules:**
  125. - No env var = all tools enabled (default)
  126. - `PARE_TOOLS` (universal) takes precedence over per-server vars
  127. - Server names use uppercase with hyphens replaced by underscores (e.g., `PARE_MY_SERVER_TOOLS`)
  128. - Whitespace around commas is ignored
  129. **Common patterns:**
  130. ```bash
  131. # Read-only git (no push, commit, add, checkout)
  132. PARE_GIT_TOOLS=status,log,diff,branch,show
  133. # Minimal npm
  134. PARE_NPM_TOOLS=install,test,run
  135. # Only specific tools across all servers
  136. PARE_TOOLS=git:status,git:diff,npm:install,test:run
  137. ```
  138. In JSON MCP config, set via the `env` key:
  139. ```json
  140. {
  141. "mcpServers": {
  142. "pare-git": {
  143. "command": "npx",
  144. "args": ["-y", "@paretools/git"],
  145. "env": {
  146. "PARE_GIT_TOOLS": "status,log,diff,show"
  147. }
  148. }
  149. }
  150. }
  151. ```
  152. ## Troubleshooting
  153. | Issue | Solution |
  154. | ----------------------------------- | --------------------------------------------------------------------------------------------------- |
  155. | `npx` not found / ENOENT on Windows | Use `cmd /c npx` wrapper (see your [client's setup guide](./docs/setup/)) |
  156. | Slow first start | Run `npx -y @paretools/git` once to cache, or install globally: `npm i -g @paretools/git` |
  157. | Node.js version error | Pare requires Node.js >= 20 |
  158. | NVM/fnm PATH issues | Use absolute path to `npx`: e.g., `~/.nvm/versions/node/v22/bin/npx` |
  159. | MCP connection timeout | Set `MCP_TIMEOUT=30000` for Claude Code, or increase `initTimeout` in client config |
  160. | Too many tools filling context | Use [tool selection](#tool-selection) env vars to limit tools, or only install the servers you need |
  161. ## Contributing
  162. Each server is a self-contained package. See [CONTRIBUTING.md](./CONTRIBUTING.md) for the full guide.
  163. ## License
  164. [MIT](./LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.