← Back to directory
P

Pare Nix

Community
Structured Nix build, develop, and flake operations as typed JSON.
GitHub source repository ↗
★ 138 Stars Category · Dev Tools Popular Source revision 57e1980e8375
29FMRS · D
Reliability
4/20
Security and permissions
4/20
Maintenance
9/20
Documentation
6/20
Setup experience
6/20

Pare Nix is part of the Pare ecosystem, focusing on providing structured output for Nix operations. It is suitable for AI agents that need to interact with Nix, but requires users to have basic Nix knowledge and be aware of resource consumption and potential risks.

Read the FMRS scoring method →

Pare Nix is an MCP server within the Pare project that wraps Nix commands (e.g., nix build, nix develop, nix flake, etc.) and returns schema-validated JSON instead of raw terminal text. It aims to provide reliable, structured data for AI agents, avoiding brittle string parsing. The server uses stdio transport and is available as the npm package @paretools/nix.

Tools

The tool list has not been reviewed yet.

Setup

Install via npm: npm install -g @paretools/nix or use npx -y @paretools/nix in your MCP client config. Then add the server configuration according to your client's guide (e.g., Claude Desktop, Cursor, etc.).

Fit and risk

Best for

  • Developers using Nix as a package manager or development environment.
  • Scenarios requiring integration of Nix operations into AI workflows.
  • MCP users who value token efficiency and reliable JSON output.

Not for

  • Projects that do not use Nix.
  • Users needing graphical or interactive Nix sessions.
  • Scripts that require unstructured text output.

Required permissions

  • Requires permission to execute Nix commands, including reading and writing to the Nix store.
  • May need network access to download Nix packages.
  • May access project flake files and other configuration files.

Risks and side effects

  • Executing Nix builds can consume significant system resources (CPU, memory, disk).
  • Failed Nix operations could lead to corrupted build artifacts or inconsistent state.
  • Misconfiguration might expose sensitive information (e.g., environment variables).

Troubleshooting

  1. If npx is not found, use the `cmd /c npx` wrapper on Windows.
  2. Slow first start: run `npx -y @paretools/nix` to pre-cache, or install globally.
  3. Node.js version errors: ensure Node.js >= 20.
  4. MCP connection timeouts: set `MCP_TIMEOUT=30000` or increase `initTimeout` in client config.

Use cases

AI agents that need to execute Nix builds and consume structured results.
Automating development environment setup (nix develop) and parsing output.
Managing Nix flakes and retrieving typed flake metadata.

Supported clients

Claude DesktopFull support