NixOS▌
by utensils
Access NixOS packages, system options, Home Manager, and nix-darwin configs with advanced caching. Explore nix package t
Provides a server for accessing NixOS packages, system options, Home Manager, and nix-darwin configurations with multi-level caching and advanced search capabilities
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / NixOS users configuring their systems
- / Home Manager users setting up dotfiles
- / macOS users with nix-darwin setups
- / Developers exploring Nix ecosystem packages
capabilities
- / Search NixOS packages and system options
- / Get detailed package and option information
- / Browse Home Manager configuration options
- / Query nix-darwin macOS-specific options
- / List available NixOS channels and statistics
- / Find options by category prefix
what it does
Search and get detailed information about NixOS packages, system options, Home Manager configurations, and nix-darwin options. Works on any system without requiring Nix installation.
about
NixOS is a community-built MCP server published by utensils that provides AI assistants with tools and capabilities via the Model Context Protocol. Access NixOS packages, system options, Home Manager, and nix-darwin configs with advanced caching. Explore nix package t It is categorized under developer tools. This server exposes 18 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install NixOS in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
NixOS is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
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
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
- 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 |
options | Browse Home Manager/Darwin options by prefix |
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 |
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) |
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="options", 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 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="options", 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
Acknowledgments
- NixHub.io - Package version history
- search.nixos.org - Official NixOS search
FAQ
- What is the NixOS MCP server?
- NixOS is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for NixOS?
- This profile displays 59 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★59 reviews- ★★★★★Chinedu Johnson· Dec 28, 2024
According to our notes, NixOS benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Ama Ramirez· Dec 20, 2024
We wired NixOS into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Dhruvi Jain· Dec 16, 2024
NixOS reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Advait Garcia· Dec 12, 2024
I recommend NixOS for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Advait Shah· Dec 4, 2024
NixOS is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Anaya Desai· Nov 23, 2024
According to our notes, NixOS benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Neel Park· Nov 19, 2024
NixOS is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Oshnikdeep· Nov 7, 2024
I recommend NixOS for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Advait Johnson· Nov 3, 2024
NixOS reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Oct 26, 2024
Strong directory entry: NixOS surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 59