mcp-nixos
MCP-NixOS is a Model Context Protocol server that gives AI assistants real-time access to NixOS package, option, and documentation data—130K+ packages, 23K+ system options, and community resources—eliminating hallucinated package names. It works on any OS (Windows, macOS, Linux) without requiring Nix installed, and integrates with Claude, Cursor, and other LLM tools via a streamlined 2-tool interface.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | utensils/mcp-nixos |
| Owner | utensils |
| Primary language | Python |
| License | MIT — OSI-approved |
| Stars | 740 |
| Forks | 39 |
| Open issues | 17 |
| Latest release | v2.4.3 (2026-04-25) |
| Last updated | 2026-07-01 |
| Source | https://github.com/utensils/mcp-nixos |
What mcp-nixos is
A Python-based MCP server exposing NixOS ecosystem data through two consolidated tools: `nix` (unified query across packages, options, flakes, Noogle, wiki, nix.dev, NixHub, and binary cache) and `nix_versions` (package history with nixpkgs commit hashes). Supports STDIO, HTTP, Docker, and Nix deployment; uses APIs and web scraping rather than local Nix evaluation, making it stateless and OS-agnostic.
Get the mcp-nixos source
Clone the repository and explore it locally.
git clone https://github.com/utensils/mcp-nixos.gitcd mcp-nixos# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Choose deployment method based on context: uvx is easiest for cloud/CI environments; Nix/Docker for reproducibility; HTTP for remote sharing. Verify which MCP client(s) your team uses (Claude, Cursor, Pi, etc.) and ensure compatibility.
- Network and API rate-limiting: Confirm your deployment can reach search.nixos.org, flakehub.com, noogle.dev, etc. Monitor or cache responses if querying frequently to avoid rate limits from upstream services.
- Context window usage is minimal (~1,030 tokens), but tool responses scale with query breadth. Test typical user queries to estimate LLM cost/latency impact in your use case.
- Nix store access (for `flake-inputs`) requires a local Nix installation on the server host; otherwise, this feature is unavailable. Ensure clarity on which deployment modes support local flake exploration.
- HTTP transport option (`MCP_NIXOS_TRANSPORT=http`) enables shared multi-client access, but note the `MCP_NIXOS_STATELESS_HTTP=1` flag disables per-client session state—verify this aligns with your concurrency model.
When to avoid it — and what to weigh
- No NixOS/Nix Usage — If your project or team does not use NixOS, Nix, Home Manager, nix-darwin, or Nixvim, this MCP server provides no value; it is purely a Nix ecosystem query layer.
- Offline-Only or Air-Gapped Environments — The server relies on external APIs (search.nixos.org, flakehub.com, noogle.dev, wiki.nixos.org, nix.dev, nixhub.io, cache.nixos.org). It will not function without internet connectivity and is unsuitable for fully offline deployments.
- High-Volume, Real-Time Search Queries — Designed for LLM-context integration, not as a production search engine. Heavy automated query loads against upstream APIs may trigger rate limiting; also lacks documented SLAs or performance guarantees.
- Strict External Dependency Isolation — The server calls third-party web services and may depend on their uptime/API stability. If your policy forbids direct external data pulls or mandates data sovereignty, this design will conflict.
License & commercial use
MIT License. Permissive; allows commercial use, modification, and distribution with minimal restrictions (retain copyright notice and license text). No liability or warranty. Suitable for enterprise and proprietary integrations.
MIT is a permissive OSI-approved license. Commercial use is explicitly allowed. However, verify compliance with third-party APIs and data sources the server queries (search.nixos.org, FlakeHub, Noogle, etc.); their terms of service may impose additional constraints on commercial usage of their data. Consult legal if commercial deployment is planned.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
MCP server acts as a network bridge between local LLM clients and external APIs. Ensure network egress is permitted and TLS validation is in place. The server queries third-party web services; confirm those are trusted. No authentication or authorization layer documented; use network-level controls (firewall, VPN) if sensitive context is involved. HTTP mode (`MCP_NIXOS_TRANSPORT=http`) exposes an endpoint—use TLS and authentication if publicly accessible. Local flake-input access reads files from the Nix store; validate file permissions and trust the local Nix installation.
Alternatives to consider
nixos-search CLI + Manual Integration
Directly invoke nixos-search or similar CLI tools and pipe output to LLM. Avoids a separate MCP server but requires custom scripting and lacks the unified tool interface; better for simple one-off queries.
Local Nix Evaluation (nix eval, nix flake show)
Use native Nix commands to query local or pinned flake data. Highly accurate for your specific lockfile but requires Nix installed, slower, and lacks internet data (FlakeHub, Noogle, wiki). Better for deterministic local configuration.
NixOS Wiki + Noogle Web UIs + Manual Browsing
Users browse documentation and search sites directly. Eliminates tooling overhead but loses LLM integration, conversational context, and reproducibility. Suitable for learning but not for automation or AI-assisted workflows.
Build on mcp-nixos with DEV.co software developers
Integrate MCP-NixOS into your LLM workflow for real-time, accurate NixOS package and option data. Deploy in minutes via uvx, Nix, Docker, or HTTP. Perfect for DevOps, SRE, and Nix developers.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
mcp-nixos FAQ
Do I need NixOS or Nix installed to run this?
How many tokens does this add to my LLM context?
Can I run this offline or air-gapped?
Which MCP clients are supported?
Work with a software development agency
From first prototype to production, DEV.co delivers software development services around tools like mcp-nixos. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across mcp servers and beyond.
Eliminate NixOS Configuration Guesswork
Integrate MCP-NixOS into your LLM workflow for real-time, accurate NixOS package and option data. Deploy in minutes via uvx, Nix, Docker, or HTTP. Perfect for DevOps, SRE, and Nix developers.