Best for
- TypeScript/JavaScript projects using npm or pnpm
- Integration with AI coding assistants that need type-safe command outputs
- Development environments that want to reduce errors from CLI output parsing
P
Pare Npm
Community
Pare npm — Structured npm/pnpm operations as typed JSON.
GitHub source repository ↗
44FMRS · D
This server focuses on providing structured JSON output for npm/pnpm operations, suitable for AI agent integration. It is not an official npm server but a community project. Its main strengths are token efficiency and reliability, but it requires Node.js 20+ and only supports npm/pnpm.
Pare npm is an MCP server from the Pare project that provides structured, typed JSON output for npm/pnpm operations. It wraps common commands like install, audit, outdated, list, and run, converting raw terminal text into schema-validated JSON to avoid brittle string parsing. The server returns two outputs: content (human-readable text) and structuredContent (type-safe JSON) for agents to process directly. It reduces token consumption and improves reliability.
Tools
install
install
audit
audit
outdated
outdated
list
list
run
run
Setup
- Use npx @paretools/init --client <client> --preset web for quick setup. 2. Or add @paretools/npm as an MCP server in your client config, e.g., using the command npx -y @paretools/npm, and set the PARE_NPM_TOOLS environment variable to specify desired tools.
Fit and risk
Not for
- Simple manual commands not requiring structured output
- Projects that need package managers other than npm/pnpm (e.g., yarn, bun) since this server only supports npm/pnpm
- Beginners unfamiliar with the MCP protocol
Required permissions
- Needs access to package.json and lock files in the project directory
- Can execute npm/pnpm commands that may consume network resources (e.g., install, audit)
- Needs to read the project's dependency tree and configuration
Risks and side effects
- Running npm install may modify node_modules and lock files; back up important data
- npm audit may return a large amount of data, but structured output may still contain sensitive info like dependency versions
- The server communicates via stdout; misconfiguration can lead to protocol conflicts
Troubleshooting
- Ensure Node.js version >= 20 (Pare requirement)
- If using npx and encountering ENOENT, try 'cmd /c npx' or the absolute path
- First start may be slow; run 'npx -y @paretools/npm' ahead of time to cache
- If MCP connection times out, set MCP_TIMEOUT=30000 or increase initTimeout in client config
- Use PARE_NPM_TOOLS env var to limit tools and reduce context usage
Use cases
AI agent workflows requiring stable, structured data from npm/pnpm commands
AI coding tools like Claude Code, Cursor that aim to reduce token usage
Automation scenarios needing reliable parsing of package installs, audits, outdated lists, etc.
Supported clients
Claude DesktopFull support