Practical overview
When it fits
Use it when an MCP-compatible assistant needs Nix ecosystem reference lookups as part of a development or configuration workflow.
Who it is for
- NixOS users who want an MCP-compatible AI assistant to look up packages, options, or documentation.
- Developers configuring an MCP client who need a Nix-focused server component.
Documented uses
- Search for NixOS packages, options, programs, or flakes.
- Retrieve details about a package or option.
- Browse Home Manager, nix-darwin, Nixvim, NVF, or Noogle resources.
- Check binary-cache status or inspect local flake inputs when Nix is available.
Requirements & limits
The README lists uvx, Nix, and Docker launch methods and says Nix is not required for API-based queries. Python 3.11 or later is indicated. The repository is public and specifies the MIT license.
- The server consolidates its listed query functions into one nix tool.
- Most documented lookups query external reference sources; local flake-input and /nix/store actions require Nix.
- Pi Coding Agent requires an MCP adapter or the project's local extension because Pi does not speak MCP natively, according to the README.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure an MCP client to launch MCP Nixos with uvx
Add the server to an MCP client's server configuration using the README's uvx launch example.
Before you start
- An MCP-compatible client that supports server configuration.
- uvx available in the environment used to launch the server.
Steps
Add a server entry named nixos to the client's mcpServers configuration.
Set command to uvx.
Set args to ["mcp-nixos"].
Expected outcome
The client configuration specifies how to launch MCP Nixos as an MCP server.
Guide limitations
- The example configures the launch command; it does not describe a particular client’s configuration interface.
- Local flake-input and /nix/store actions require Nix.
Run MCP Nixos over HTTP
Start the server using the documented HTTP transport settings.
Before you start
- The mcp-nixos command available in the environment.
Steps
Set MCP_NIXOS_TRANSPORT=http.
Set MCP_NIXOS_HOST=127.0.0.1 and MCP_NIXOS_PORT=8000.
Run mcp-nixos.
Expected outcome
The README's example configures an HTTP MCP endpoint at http://127.0.0.1:8000/mcp.
Guide limitations
- The README identifies /mcp as the default endpoint path; it does not describe client-specific connection steps.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- utensils/mcp-nixos · Official homepage title · retained in its source language

