Query NixOS Package and Configuration Data
MCP-NixOS gives an AI assistant real-time NixOS, Home Manager, and nix-darwin package and option data, in just two tools.
3.0.1Add to Favorites
Why it matters
Access real-time information on over 130,000 NixOS packages, 22,000 configuration options, and related ecosystem data. This asset empowers AI assistants with accurate, up-to-date details for development and system management.
Outcomes
What it gets done
Search NixOS packages, options, and programs.
Retrieve detailed information on NixOS packages and configuration options.
Access Home Manager and nix-darwin configuration details.
View package version history and ecosystem statistics.
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-mcp-nixos | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Capabilities
Tools your agent gets
Search for packages, options, or programs by query, type, and channel
Get detailed information about packages or options
Get the count of packages and options for a channel
List all available NixOS channels
Search community flakes
Get flakes ecosystem statistics
Get package version history with commit hashes
Smart search for specific package versions
Overview
MCP-NixOS MCP Server
MCP-NixOS is an MCP server that gives an AI assistant real-time, accurate data on NixOS packages and options, Home Manager, nix-darwin, Nixvim, NVF, FlakeHub, and Noogle function signatures, through just two consolidated tools. It needs no Nix installation to run, since it queries public APIs directly. Use it whenever an agent needs to verify a real Nix package or option name, check binary cache status, or find a package's version history. Only local flake-input exploration needs an actual Nix installation.
What it does
MCP-NixOS gives an AI assistant accurate, real-time answers about the Nix ecosystem instead of hallucinated package or option names: 130K+ NixOS packages, 23K+ NixOS options, 5K+ Home Manager options, 1K+ nix-darwin settings, 5K+ Nixvim options, 2.4K+ NVF Neovim options, 600+ FlakeHub flakes, 2K+ Noogle function signatures, NixOS Wiki and nix.dev documentation, historical package versions with commit hashes, and binary cache status - all queried live from their respective sources rather than baked into the model's training data.
When to use - and when NOT to
Use it whenever an agent needs to write or verify a Nix configuration, find the right package or option name, check whether a package version is cached, or explore a project's pinned flake inputs. It requires no Nix or NixOS installation to run - it's just querying public APIs, and works the same on Windows, macOS, or Linux. Only the local flake-inputs feature, exploring your own pinned dependencies from the Nix store, needs an actual Nix installation to have something to read.
Capabilities
The whole surface is two tools, consolidated down from an earlier 17 to keep the tool-definition footprint to roughly 1,030 tokens. nix(action, query, source, ...) handles search, detailed info, stats, browsing, channel listing, flake-input exploration, and binary-cache checks across eleven sources: nixos, home-manager, darwin, flakes, flakehub, nixvim, nvf, noogle, wiki, nix-dev, and nixhub. nix_versions(package, version, limit) returns a package's historical versions with nixpkgs commit hashes for reproducible builds, platform availability, and metadata like license and homepage. NVF option queries accept either the canonical vim.* path or the programs.nvf.settings.vim.* module-wrapper path, normalized automatically either way.
How to install
uvx mcp-nixos
No separate Nix installation is required for this. It also runs via Nix (nix run github:utensils/mcp-nixos), Docker (docker run --rm -i ghcr.io/utensils/mcp-nixos), or as a remote HTTP MCP server (MCP_NIXOS_TRANSPORT=http mcp-nixos). It's declaratively installable through nixpkgs for NixOS, Home Manager, or nix-darwin configurations, and has documented setup paths for the Pi coding agent via pi-mcp-adapter or a project-local .pi/extensions/mcp-nixos.ts extension the repository ships directly. It is MIT-licensed.
Who it's for
Developers writing or maintaining Nix, NixOS, Home Manager, or nix-darwin configurations who want an AI assistant grounded in real, current package and option data instead of guessing names that don't exist. It draws on data sources including search.nixos.org, NixHub.io, FlakeHub, Noogle, and the NuschtOS option-search infrastructure that powers its Nixvim support, plus the published unstable documentation behind its NVF Neovim option coverage.
Source README
MCP-NixOS - Because Your AI Shouldn't Hallucinate Package Names
Quick Start
🚨 No Nix/NixOS Required! Works on any system - Windows, macOS, Linux. You're just querying APIs.
Option 1: uvx (Recommended)
{
"mcpServers": {
"nixos": {
"command": "uvx",
"args": ["mcp-nixos"]
}
}
}
Option 2: Nix
{
"mcpServers": {
"nixos": {
"command": "nix",
"args": ["run", "github:utensils/mcp-nixos", "--"]
}
}
}
Option 3: Docker
{
"mcpServers": {
"nixos": {
"command": "docker",
"args": ["run", "--rm", "-i", "ghcr.io/utensils/mcp-nixos"]
}
}
}
Your AI now has access to real NixOS data instead of making things up. You're welcome.
Option 4: HTTP (Remote MCP)
FastMCP supports running this server over HTTP at a URL (the MCP endpoint defaults to /mcp).
# Run an HTTP MCP server at http://127.0.0.1:8000/mcp
MCP_NIXOS_TRANSPORT=http MCP_NIXOS_HOST=127.0.0.1 MCP_NIXOS_PORT=8000 mcp-nixos
STDIO (default):
MCP_NIXOS_TRANSPORT=stdio mcp-nixos
Custom path:
MCP_NIXOS_TRANSPORT=http MCP_NIXOS_PATH=/api/mcp mcp-nixos
Stateless HTTP (disables per-client session state):
MCP_NIXOS_TRANSPORT=http MCP_NIXOS_STATELESS_HTTP=1 mcp-nixos
Option 5: Pi Coding Agent
Pi does not speak MCP natively. Two supported paths:
A. pi-mcp-adapter (recommended - speaks MCP, single source of truth):
pi install npm:pi-mcp-adapter
Then add to ~/.pi/agent/mcp.json:
{
"mcpServers": {
"nixos": {
"command": "uvx",
"args": ["mcp-nixos"],
"lifecycle": "lazy"
}
}
}
B. Project-local extension (clone + run): this repo ships .pi/extensions/mcp-nixos.ts, auto-loaded when you run pi in the cloned repo. Optional: cd .pi && npm install for editor type resolution. Pi runs it either way.
What Is This?
An MCP server providing accurate, real-time information about:
- NixOS packages - 130K+ packages that actually exist
- NixOS options - 23K+ ways to configure your system
- Home Manager - 5K+ options for dotfile enthusiasts
- nix-darwin - 1K+ macOS settings Apple doesn't document
- Nixvim - 5K+ options for Neovim configuration via NuschtOS search
- NVF - 2.4K+ Neovim options from its published unstable documentation
- FlakeHub - 600+ flakes from FlakeHub.com registry
- Noogle - 2K+ Nix functions with type signatures via noogle.dev
- NixOS Wiki - Community documentation and guides from wiki.nixos.org
- nix.dev - Official Nix tutorials and guides from nix.dev
- Package versions - Historical versions with commit hashes via NixHub.io
- Binary cache status - Check if packages are cached on cache.nixos.org with download sizes
- Local flake inputs - Explore your pinned flake dependencies directly from the Nix store (requires Nix)
The Tools
Just two. We consolidated 17 tools into 2 because your AI's context window isn't infinite.
~1,030 tokens total. That's it. While other MCP servers are hogging your context like it's Black Friday, we're sipping minimalist tea in the corner. Your AI gets NixOS superpowers without the bloat.
nix - Unified Query Tool
One tool to rule them all:
nix(action, query, source, type, channel, limit)
| Action | What it does |
|---|---|
search |
Search packages, options, programs, or flakes |
info |
Get detailed info about a package or option |
stats |
Get counts and categories |
browse |
Browse Home Manager, Darwin, Nixvim, NVF, or Noogle by prefix (legacy alias: options) |
channels |
List available NixOS channels |
flake-inputs |
Explore local flake inputs from Nix store |
cache |
Check binary cache status for packages |
| Source | What it queries |
|---|---|
nixos |
Packages, options, programs |
home-manager |
Home Manager options |
darwin |
nix-darwin options |
flakes |
Community flakes (search.nixos.org) |
flakehub |
FlakeHub registry (flakehub.com) |
nixvim |
Nixvim Neovim configuration options |
nvf |
NVF Neovim configuration options (latest unstable docs) |
noogle |
Nix function signatures and docs (noogle.dev) |
wiki |
NixOS Wiki articles (wiki.nixos.org) |
nix-dev |
Official Nix documentation (nix.dev) |
nixhub |
Package metadata and store paths (nixhub.io) |
NVF results use canonical vim.* option paths. Queries may also use the shorthandprograms.nvf.vim.* or the NixOS/Home Manager module pathprograms.nvf.settings.vim.*; both are normalized automatically.
Examples:
# Search NixOS packages
nix(action="search", query="firefox", source="nixos", type="packages")
# Get package info
nix(action="info", query="firefox", source="nixos", type="package")
# Search Home Manager options
nix(action="search", query="git", source="home-manager")
# Browse darwin options
nix(action="browse", source="darwin", query="system.defaults")
# Search Nixvim options
nix(action="search", query="telescope", source="nixvim")
# Get Nixvim option info
nix(action="info", query="plugins.telescope.enable", source="nixvim")
# Search NVF options
nix(action="search", query="vim.languages.nix", source="nvf")
# Get NVF option info using a module wrapper path
nix(action="info", query="programs.nvf.settings.vim.languages.nix.enable", source="nvf")
# Browse NVF options below a prefix
nix(action="browse", query="programs.nvf.vim.languages.nix", source="nvf")
# Search FlakeHub
nix(action="search", query="nixpkgs", source="flakehub")
# Get FlakeHub flake info
nix(action="info", query="NixOS/nixpkgs", source="flakehub")
# Search Noogle for Nix functions
nix(action="search", query="mapAttrs", source="noogle")
# Get Noogle function info
nix(action="info", query="lib.attrsets.mapAttrs", source="noogle")
# Browse Noogle function categories
nix(action="browse", source="noogle", query="lib.strings")
# Search NixOS Wiki
nix(action="search", query="nvidia", source="wiki")
# Get Wiki page info
nix(action="info", query="Flakes", source="wiki")
# Search nix.dev documentation
nix(action="search", query="packaging tutorial", source="nix-dev")
# Search NixHub for package metadata
nix(action="search", query="nodejs", source="nixhub")
# Get detailed package info from NixHub (license, homepage, store paths)
nix(action="info", query="python", source="nixhub")
# Check binary cache status
nix(action="cache", query="hello")
# Check cache for specific version
nix(action="cache", query="python", version="3.12.0")
# Check cache for specific system
nix(action="cache", query="firefox", system="x86_64-linux")
# Get stats
nix(action="stats", source="nixos", channel="stable")
# List local flake inputs (requires Nix)
nix(action="flake-inputs", type="list")
# Browse files in a flake input
nix(action="flake-inputs", type="ls", query="nixpkgs:pkgs/by-name")
# Read a file from a flake input
nix(action="flake-inputs", type="read", query="nixpkgs:flake.nix")
nix_versions - Package Version History
Find historical versions with nixpkgs commit hashes. Output includes:
- Package metadata (license, homepage, programs) when available
- Platform availability per version (Linux/macOS)
- Nixpkgs commit hash for reproducible builds
- Attribute path for Nix expressions
nix_versions(package, version, limit)
Examples:
# List recent versions with metadata
nix_versions(package="python", limit=5)
# Find specific version
nix_versions(package="nodejs", version="20.0.0")
Installation
You DON'T need Nix installed. This runs anywhere Python runs.
# Run directly (no install)
uvx mcp-nixos
# Or install
pip install mcp-nixos
For Nix users:
nix run github:utensils/mcp-nixos
nix profile install github:utensils/mcp-nixos
Declarative Installation (NixOS / Home Manager / nix-darwin)
mcp-nixos is available in nixpkgs:
# NixOS (configuration.nix)
environment.systemPackages = [ pkgs.mcp-nixos ];
# Home Manager (home.nix)
home.packages = [ pkgs.mcp-nixos ];
# nix-darwin (darwin-configuration.nix)
environment.systemPackages = [ pkgs.mcp-nixos ];
Or use the flake directly with the provided overlay:
# flake.nix
{
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
mcp-nixos.url = "github:utensils/mcp-nixos";
};
outputs = { self, nixpkgs, mcp-nixos, ... }: {
# Example: NixOS configuration
nixosConfigurations.myhost = nixpkgs.lib.nixosSystem {
system = "x86_64-linux";
modules = [{
nixpkgs.overlays = [ mcp-nixos.overlays.default ];
environment.systemPackages = [ pkgs.mcp-nixos ];
}];
};
# Example: Home Manager standalone
homeConfigurations.myuser = home-manager.lib.homeManagerConfiguration {
pkgs = import nixpkgs {
system = "x86_64-linux";
overlays = [ mcp-nixos.overlays.default ];
};
modules = [{
home.packages = [ pkgs.mcp-nixos ];
}];
};
};
}
Development
nix develop # Enter dev shell
nix build # Build package
pytest tests/ # Run tests
ruff check . # Lint
ruff format . # Format
mypy mcp_nixos/ # Type check
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.