← Back to directory
P

Pare Npm

Community
Pare npm — Structured npm/pnpm operations as typed JSON.
Category
Dev Tools #315 of 438
Stars
★ 138 Popular
Transport
stdio (local process)
Runtime
Node.js 20+
Credentials
No credential needed
License
MIT
Last commit
Tools
5
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.

Strongest · Maintenance 12/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
7/20
Maintenance
12/20
Documentation
9/20
Setup experience
10/20
Why each score
Reliability 6/20
Evidence is limited to the manifest and the general README. The manifest declares @paretools/npm 0.22.0 over stdio and describes structured install/audit/outdated/list/run operations, so a happy path is plausible. No source, tests, or CI workflow for packages/server-npm was supplied, so the init handshake and tool-to-behavior correspondence cannot be verified; deducted for missing execution evidence per static calibration.
Security and permissions 7/20
No red-line risks are evident. npm install/run involve network access and script execution, and audit contacts the registry, but the documentation does not show per-server confirmation, least-privilege, or command scoping, nor does it describe .npmrc credential handling. Main risks are visible but permission/confirmation evidence is incomplete.
Maintenance 12/20
The repository is not archived, the manifest shows version 0.22.0, an MIT license is present, and the README displays CI, Codecov and OpenSSF badges, indicating ongoing maintenance. However, no commit history, release notes, or security-response channel was provided, so governance and update-path evidence is incomplete.
Documentation 9/20
The README offers project-wide install, configuration, tool-filtering and troubleshooting guidance, but lacks packages/server-npm-specific tool parameters, output schemas, authentication, and limits; the linked tool-schema docs are not part of the supplied material, so deduction applies.
Setup experience 10/20
The README gives a quick-start flow, presets, client config examples and a Node.js >=20 requirement, making the overall installation path clear. A concrete MCP config example for the npm server is not shown (the example uses git), requiring inference, and no execution evidence supports a score above 15.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the network

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

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

Setup

Before you start

Runtime:Node.js 20+

Other optional settings (2)
PARE_NPM_TOOLS optional Optional per-server filter limiting which tools the npm server registers, e.g. install,test,run; unset means all tools.
PARE_TOOLS optional Optional universal filter across all Pare servers in server:tool comma-separated format, e.g. git:status,npm:install; takes precedence over per-server vars.
  1. 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.

Check that it works

Confirm the tools install, audit, outdated, list and run appear in the client's tool list, then ask the agent to run npm list — a structured JSON dependency listing proves the connection works.

Troubleshooting

  1. Ensure Node.js version >= 20 (Pare requirement)
  2. If using npx and encountering ENOENT, try 'cmd /c npx' or the absolute path
  3. First start may be slow; run 'npx -y @paretools/npm' ahead of time to cache
  4. If MCP connection times out, set MCP_TIMEOUT=30000 or increase initTimeout in client config
  5. Use PARE_NPM_TOOLS env var to limit tools and reduce context usage

Things to try

Once connected, you can ask your AI assistant things like:

  • Install all dependencies from package.
  • Check this project's dependencies for known security vulnerabilities
  • Show me which dependencies have newer versions available
  • Run the test script and summarize the results as JSON

Tools 5

install writes
install
audit read-only
audit
outdated read-only
outdated
list read-only
list
run writes
run

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 Desktop

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

Source revision 57e1980e8375 Data synced 2026-10-13 Read the FMRS scoring method