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.
P
Pare Nix
Community
Structured Nix build, develop, and flake operations as typed JSON.
- Category
- Dev Tools #416 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js 20+
- Credentials
- No credential needed
- License
- MIT
- Last commit
29FMRS · D
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.
Strongest · Maintenance 9/20 Weakest · Reliability 4/20
Why each score
- Reliability 4/20
- The only evidence supplied is the repo-level README and the server-nix manifest; no server-nix source code, full tool list, CI, or tests were provided. The manifest is internally consistent and the README claims structuredContent JSON output, but the MCP init/tool-list handshake and actual tool behavior cannot be verified, and there is no reproducible execution evidence, so the score is conservatively reduced.
- Security and permissions 4/20
- No red-line issues such as malware, credential theft, destructive defaults, or leaked secrets are evident, but no security model specific to server-nix is documented. Nix build/develop/flake operations can fetch from the network and mutate the local store; the manifest and README do not describe confirmation gating, least-privilege scoping, or data-flow boundaries, so the score remains low.
- Maintenance 9/20
- The repository is not archived, is MIT-licensed, and the manifest references version 0.22.0, indicating versioned releases. However, the supplied material does not evidence commit/release cadence, dependency-update processes, or a security-response channel, so full marks are not justified. Stars are treated only as discovery signals and add no points.
- Documentation 6/20
- The README covers general architecture, quick setup, tool filtering, and troubleshooting, but server-nix-specific tool parameters, output schema examples, limitations, and Nix-specific troubleshooting are absent from the supplied material. Links to docs/tool-schemas cannot be verified in a static review, so deductions apply for missing evidence.
- Setup experience 6/20
- The manifest exposes the npm package @paretools/nix over stdio, and the README shows generic npx installation and client configuration examples. There is no server-nix-specific launch command, client config snippet, platform-compatibility note, or executable verification. Given the static review ceiling of 15 for setup, the available evidence supports only 6.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessRuns commands or code
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).
Setup
Before you start
Runtime：Node.js 20+
Other optional settings (1)
PARE_TOOLS
Optional universal tool filter across all Pare servers, in server:tool format (e.g. git:status,npm:install); takes precedence over per-server variables.
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.).
Check that it works
The pare-nix server's nix-related tools should appear in your client's tool list; you can also run `npx @paretools/init doctor` to validate the connection.
Troubleshooting
- If npx is not found, use the `cmd /c npx` wrapper on Windows.
- Slow first start: run `npx -y @paretools/nix` to pre-cache, or install globally.
- Node.js version errors: ensure Node.js >= 20.
- MCP connection timeouts: set `MCP_TIMEOUT=30000` or increase `initTimeout` in client config.
Things to try
Once connected, you can ask your AI assistant things like:
- Run nix build on this flake and return the result as JSON
- List the dev shells in this flake and what packages each includes
- Run nix flake check and summarize any errors in structured form
- Show the inputs in my flake.nix and tell me which are outdated
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 Desktop
Listed from the project's documentation, not tested by this site.
Overview
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.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method