MCP Catalogs
Home

Pare

by Dave-London·121·Score 49

MCP servers that transform CLI tools into structured JSON outputs for AI agents, reducing token usage by up to 95%.

developer-toolsops-infraai-llm
10
Forks
14
Open issues
this month
Last commit
2d ago
Indexed

Overview

Pare provides a suite of MCP servers that wrap common developer tools (git, npm, docker, test runners, etc.) and return clean, schema-validated JSON instead of raw terminal text. This eliminates the need for fragile string parsing while significantly reducing token consumption. The servers offer both human-readable text and structured JSON content, allowing agents to work with reliable, typed data that's consistent across platforms, tool versions, and locales.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Automating git operations and status checks in development workflows
you:Integrating npm package management with AI coding assistants
you:Running and analyzing test results through structured JSON output
you:How does Pare reduce token usage?
you:Can I select which tools to register?

When to choose this

Choose Pare when working with AI agents that need reliable, structured output from development tools, especially when token efficiency is important or when working across different platforms.

When NOT to choose this

Don't choose Pare if you need raw terminal output with full formatting, or if your workflow depends on parsing specific terminal text patterns that would be lost in the JSON conversion.

Tools this server exposes

12 tools extracted from the README
  • git:status

    Get structured git status information

  • git:log

    Get structured git commit history

  • git:diff

    Get structured git diff output

  • git:show

    Get structured information about a specific commit

  • npm:install

    Get structured output from npm install

  • npm:test

    Get structured output from npm test

  • docker:build

    Get structured output from docker build

  • test:run

    Get structured output from test runners

  • lint:run

    Get structured output from linters

  • k8s:get

    Get structured output from kubectl get

  • infra:plan

    Get structured output from terraform plan

  • security:scan

    Get structured output from security scanners

Note: Tool names inferred from category table and examples. No explicit tool listing in README.

Comparable tools

nix-mcpshell-mcpgithub-cli

Installation

Install Pare MCP servers using:

# Quick setup (non-interactive)
npx @paretools/init --client claude-code --preset web

# Add agent rules to your project
cat node_modules/@paretools/init/rules/CLAUDE.md >> CLAUDE.md

# Validate installation
npx @paretools/init doctor

For Claude Desktop, add to config.json:

{
  "mcpServers": {
    "pare-git": {
      "command": "npx",
      "args": ["-y", "@paretools/git"]
    },
    "pare-npm": {
      "command": "npx", 
      "args": ["-y", "@paretools/npm"]
    }
  }
}

FAQ

How does Pare reduce token usage?
Pare transforms verbose CLI output into structured JSON, which is typically 46-95% more compact than raw terminal text. For example, a 'docker build' command that outputs 373 raw tokens only produces 20 tokens when processed through Pare.
Can I select which tools to register?
Yes, you can filter tools using environment variables like PARE_GIT_TOOLS=status,log or PARE_TOOLS=git:status,npm:install to limit which tools are available to the agent.

Compare Pare with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.