What can you do with this server?

The MCP-NixOS server provides accurate, real-time access to NixOS, Home Manager, and nix-darwin resources for AI assistants. * Search capabilities: Search for NixOS packages, options, or programs, including version-specific data across different channels (unstable, stable, and older) * Detailed information: Retrieve comprehensive details about specific NixOS packages and options * Home Manager support: Search configuration options, get detailed information, list top-level categories, and search by prefix * nix-darwin access: Interact with macOS configurations, including searching options and retrieving information about system and services * Statistics: Obtain usage data about available NixOS packages/options, Home Manager options, and nix-darwin configurations * Structured searches: Perform customizable searches with limits and channel preferences This server helps AI assistants provide accurate NixOS-related information, reducing hallucinations and incorrect package suggestions.

Which integrations are available for this server?

Integrates with Codecov for tracking code coverage statistics from the project's test suite, with links to coverage reports. Connects to the NixOS Elasticsearch API to query package information and system options with field-specific search boosts, multiple channel support, and error handling. Offers specific integration for Firefox configuration in Home Manager, enabling access to Firefox profiles and settings information through dedicated search and info tools. Provides access to Git configuration options in Home Manager, allowing AI assistants to retrieve information about Git username and other configuration settings. Provides nix-darwin integration for macOS configuration options, allowing AI assistants to search and retrieve information about system defaults, services, and other macOS-specific settings that can be configured through nix-darwin. Provides access to NGINX service configuration options in NixOS, allowing AI assistants to retrieve information about NGINX service settings. Provides real-time access to NixOS packages and system options via the Elasticsearch API, allowing AI assistants to search and retrieve accurate information about available packages, their metadata, and system configuration options across multiple NixOS channels. Enables access to PostgreSQL service configuration options in NixOS, allowing AI assistants to search and retrieve information about PostgreSQL service settings. Provides integration with PyPI for package distribution, with version tracking and Python version compatibility information. Offers integration with the yabai window manager configuration options in nix-darwin, providing access to service settings for macOS window management. Provides access to Zsh shell configuration options in Home Manager, allowing AI assistants to search and retrieve information about Zsh settings.

How do I use mcp-nixos?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-nixos search for neovim packages in nixos" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

mcp-nixos

by utensils

Overview Schema Related Servers Score Discussions

Python

Remote

MCP-NixOS - Because Your AI Shouldn't Hallucinate Package Names

MCP Toplist

codecov PyPI FlakeHub Python 3.11+ CodeRabbit Pull Request Reviews Built with Claude

Quick Start

🚨 No Nix/NixOS Required! Works on any system - Windows, macOS, Linux. You're just querying APIs.

Option 1: uvx (Recommended)

Install MCP Server

{
  "mcpServers": {
    "nixos": {
      "command": "uvx",
      "args": ["mcp-nixos"]
    }
  }
}

Option 2: Nix

Install MCP Server

{
  "mcpServers": {
    "nixos": {
      "command": "nix",
      "args": ["run", "github:utensils/mcp-nixos", "--"]
    }
  }
}

Option 3: Docker

Install MCP Server

{
  "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.

Related MCP server: Grounded Code MCP

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 shorthand programs.nvf.vim.* or the NixOS/Home Manager module path programs.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

Acknowledgments

NixHub.io - Package version history
search.nixos.org - Official NixOS search
FlakeHub - Flake registry by Determinate Systems
Jetify - Creators of Devbox and NixHub
Noogle - Nix function search engine
NuschtOS - Static option search infrastructure powering Nixvim support
Nixvim - Neovim configuration framework for Nix
NVF - Neovim configuration framework and published option catalogue

License

MIT - Because sharing is caring.

Created by James Brink. Maintained by mass̶o̶c̶h̶i̶s̶t̶s̶ enthusiasts who enjoy Nix.

Available Tools

2 tools

nixA

Query NixOS, Home Manager, Darwin, FlakeHub, flakes, Nixvim, NVF, Wiki, nix.dev, Noogle, NixHub.

Use this tool for anything touching nixpkgs, Nix channels, flakes, NixOS / home-manager / darwin options, the binary cache, or /nix/store paths — even when you think you know the answer. Your training data lags nixpkgs by months. Prefer this over nix search, scraping search.nixos.org, or running gh api against NixOS/nixpkgs.

INTENTS → CALLS (copy the JSON "is package X in channel Y?" "search for package X" "which channels are available?" "which commit did channel "search NixOS options for X" "get option details for X" "home-manager option for X" "darwin option for X" "nixvim option for X" "NVF option for X" "what programs does pkg "count packages/options" "browse hm option tree under P" "does X have a binary cache?" "search the NixOS wiki for X" "search nix.dev docs" "read a nix.dev page" "list inputs of current flake" "ls inside flake input X" "read /nix/store/... file" "ls /nix/store/... dir" shape exactly): → {"action": "info", "query": "X", "channel": "Y"} → {"action": "search", "query": "X"} → {"action": "channels"} X index?" → {"action": "channels"} (indexed commit shown when known; branch HEAD otherwise — label matters) → {"action": "search", "query": "X", "type": "options"} → {"action": "info", "query": "X", "type": "option"} → {"action": "search", "query": "X", "source": "home-manager"} → {"action": "search", "query": "X", "source": "darwin"} → {"action": "search", "query": "X", "source": "nixvim"} → {"action": "search", "query": "X", "source": "nvf"} X provide?" → {"action": "search", "query": "X", "type": "programs"} → {"action": "stats"} → {"action": "browse", "query": "P", "source": "home-manager"} → {"action": "cache", "query": "X"} → {"action": "search", "query": "X", "source": "wiki"} → {"action": "search", "query": "X", "source": "nix-dev"} → {"action": "info", "query": "tutorials/nix-language", "source": "nix-dev"} → {"action": "flake-inputs"} → {"action": "flake-inputs", "type": "ls", "query": "X"} → {"action": "store", "type": "read", "query": "/nix/store/..."} → {"action": "store", "type": "ls", "query": "/nix/store/..."}

For package version history ("which commit shipped firefox 150?", "when was node 18 added?"), use the separate nix_versions tool — it returns commit hashes, attribute paths, and dates.

Notes:

To search NixOS options, use action=search with type=options. Do NOT use action=browse for source=nixos — browse is for walking a pre-indexed option tree and only works with home-manager, darwin, nixvim, nvf, or noogle.
For source=nvf, canonical option paths are vim.. The shorthand programs.nvf.vim. and NixOS/Home Manager module path programs.nvf.settings.vim.* are normalized automatically.
For source=nix-dev, action=info returns the page markdown. The query may be a bare docname like "tutorials/nix-language", the URL printed by nix-dev search ("https://nix.dev/tutorials/nix-language"), or a rendered ".html" URL.
action=info for packages matches on the exact attribute path first, then the exact pname. If multiple packages share a pname (e.g. firefox / firefox-esr / firefox-mobile), the canonical attribute wins and the response flags the disambiguation explicitly.
Omit parameters you don't need; do not pass empty strings for optional args.

ParametersJSON Schema

Name	Required	Description	Default
`type`	No	Sub-type of query. For source=nixos with action=search, one of: packages, options, programs, flakes. For source=nixos with action=info, one of: package, option. For flake-inputs, one of: list, ls, read. For store, one of: ls, read. Ignored by most other sources.	packages
`limit`	No	Max results. 1-100 (or 1-2000 for flake-inputs/store read).
`query`	No	Search term for 'search', exact name for 'info', prefix path for 'browse'. For flake-inputs: input_name or input:path. For store: absolute /nix/store/ path. Leave empty for 'stats'/'channels'.
`action`	Yes	One of: search, info, stats, browse, channels, flake-inputs, cache, store. Use 'search' for keyword lookup, 'info' for details about a specific name, 'browse' to walk an option hierarchy by prefix (home-manager/darwin/nixvim/nvf/noogle only). 'store' reads files or lists directories at an explicit /nix/store/ path.
`source`	No	Data source for search/info/stats/browse/cache. One of: nixos (default), home-manager, darwin, flakes, flakehub, nixvim, nvf, wiki, nix-dev, noogle, nixhub. For action=flake-inputs, this may instead be a path to a flake directory; omit/default to use the current project. Ignored by action=store.	nixos
`system`	No	Only used by action=cache. System arch e.g. x86_64-linux. Empty for all.
`channel`	No	NixOS channel: unstable (default), stable, or a release like 25.05.	unstable
`version`	No	Only used by action=cache. Package version (default: latest).	latest

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and excels. It discloses nuanced behaviors: how `browse` only works with certain sources, the exact matching semantics for `action=info` (attribute path first, then pname, with disambiguation flags), normalization for NVF paths, accepted URL forms for nix-dev, and the policy to omit parameters rather than pass empty strings. This is exceptionally transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every section earns its place: a concise summary, clear usage guidance, a structured INTENTS → CALLS table, and focused notes that resolve common pitfalls. It is well front-loaded with the core purpose, and the format makes the dense information scannable. Nothing feels redundant or wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, multiple sources, multiple actions) and zero annotations, the description is remarkably complete. It covers purpose, usage context, behavioral details, parameter semantics, and even differentiates from the sibling tool. The presence of an output schema means the description need not explain return structures, and it doesn't, staying appropriately scoped.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already provides 100% parameter descriptions, the description goes far beyond by mapping natural-language intents to exact JSON shapes (e.g., 'is package X in channel Y?' -> {"action": "info", "query": "X", "channel": "Y"}). It also clarifies valid combinations, defaults, and special behaviors (e.g., 'source' can be a path for flake-inputs, 'limit' ranges differ per action). This adds substantial semantic value over the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb ('Query') and enumerates the full set of resources (NixOS, Home Manager, Darwin, FlakeHub, flakes, Nixvim, NVF, Wiki, nix.dev, Noogle, NixHub). It also distinguishes itself from the sibling tool `nix_versions` by explicitly routing package version history queries there, making the purpose unambiguous and well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance ('Use this tool for anything touching nixpkgs... even when you think you know the answer') and explicitly names alternatives to prefer over ('Prefer this over `nix search`, scraping search.nixos.org, or running `gh api`'). It also gives a clear exclusion: package version history should go to `nix_versions`. This is textbook usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

nix_versionsC

Get package version history from NixHub.io.

ParametersJSON Schema

Name	Required	Description
`limit`	No	1-50
`package`	Yes	Package name
`version`	No	Specific version to find

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description should disclose behavioral traits. It only states it retrieves version history, but offers no details about pagination, error handling, rate limits, or what constitutes a valid response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no fluff. It is concise but could be slightly expanded without losing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return value documentation is not required. However, given three parameters and no annotations, the description is minimal and leaves gaps in understanding the tool's full behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the descriptions for parameters ('Package name', 'Specific version to find', '1-50') are clear. However, the tool description adds no extra value beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Get) and resource (package version history from NixHub.io). It conveys the purpose effectively but does not differentiate from the sibling tool 'nix'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description lacks context about prerequisites, limitations, or comparison to the sibling tool 'nix'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

1 tool updatev3.0.0Aug 5, 2026

Changednix2 fields changed

changedInput schema / properties / action / description

Previous value: -"One of: search, info, stats, browse, channels, flake-inputs, cache, store. Use 'search' for keyword lookup, 'info' for details about a specific name, 'browse' to walk an option hierarchy by prefix (home-manager/darwin/nixvim/noogle only). 'store' reads files or lists directories at an explicit /nix/store/ path."New value: +"One of: search, info, stats, browse, channels, flake-inputs, cache, store. Use 'search' for keyword lookup, 'info' for details about a specific name, 'browse' to walk an option hierarchy by prefix (home-manager/darwin/nixvim/nvf/noogle only). 'store' reads files or lists directories at an explicit /nix/store/ path."

changedInput schema / properties / source / description

Previous value: -"Data source for search/info/stats/browse/cache. One of: nixos (default), home-manager, darwin, flakes, flakehub, nixvim, wiki, nix-dev, noogle, nixhub. For action=flake-inputs, this may instead be a path to a flake directory; omit/default to use the current project. Ignored by action=store."New value: +"Data source for search/info/stats/browse/cache. One of: nixos (default), home-manager, darwin, flakes, flakehub, nixvim, nvf, wiki, nix-dev, noogle, nixhub. For action=flake-inputs, this may instead be a path to a flake directory; omit/default to use the current project. Ignored by action=store."

20 tool updatesv2.1.0Apr 30, 2026
- Removeddarwin_info
- Removeddarwin_list_options
- Removeddarwin_options_by_prefix
- Removeddarwin_search
- Removeddarwin_stats
- Removedhome_manager_info
- Removedhome_manager_list_options
- Removedhome_manager_options_by_prefix
- Removedhome_manager_search
- Removedhome_manager_stats
- Addednix
- Addednix_versions
- Removednixhub_find_version
- Removednixhub_package_versions
- Removednixos_channels
- Removednixos_flakes_search
- Removednixos_flakes_stats
- Removednixos_info
- Removednixos_search
- Removednixos_stats
18 tool updatesAug 18, 2025
- First observeddarwin_info
- First observeddarwin_list_options
- First observeddarwin_options_by_prefix
- First observeddarwin_search
- First observeddarwin_stats
- First observedhome_manager_info
- First observedhome_manager_list_options
- First observedhome_manager_options_by_prefix
- First observedhome_manager_search
- First observedhome_manager_stats
- First observednixhub_find_version
- First observednixhub_package_versions
- First observednixos_channels
- First observednixos_flakes_search
- First observednixos_flakes_stats
- First observednixos_info
- First observednixos_search
- First observednixos_stats

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Disambiguation5/5

Only two tools, and they have clearly distinct purposes: `nix` is the general-purpose query tool for all Nix-related lookups, while `nix_versions` is explicitly scoped to package version history. The description even directs users to `nix_versions` for history queries, eliminating any ambiguity.

Naming Consistency4/5

Both tool names share the 'nix' prefix, showing a loose consistency, but one uses a single word (`nix`) and the other uses an underscore compound (`nix_versions`). This is a minor deviation from a more uniform pattern, but not confusing.

Tool Count3/5

With only 2 tools, the count is on the low end, but the primary `nix` tool is a powerful monolith covering dozens of actions. It feels thin compared to typical servers, yet the consolidated design makes it functional. Borderline appropriate.

Completeness4/5

The `nix` tool covers a broad range of Nix domain operations: package and option search, channels, flakes, store paths, wiki, and nix.dev docs. `nix_versions` adds version history. Together they handle most query-centric needs, though mutations or builds are outside scope, leaving minor gaps.

Maintenance

ActivityMaintained

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
driflyte-mcp-server
com.driflyte
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Search Web Scraping Knowledge & Memory
211
OpenRouter AFeaturedOAuth
ai.openrouter.mcp
The OpenRouter MCP server plugs OpenRouter into the AI tools you already use. Once connected, your assistant can pull live OpenRouter data (models, prices, your credits, rankings, and docs) and send quick test messages, all without leaving your editor.
AI & Machine Learning
221
Mercado PagoOAuth
com.mercadopago.mcp
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Finance E-commerce & Retail App Automation
2

Related MCP Servers

Context7 MCP
Documentation Access Developer Tools RAG Systems
upstash
A
license
A
quality
A
maintenance
A Model Context Protocol server that fetches up-to-date, version-specific documentation and code examples from libraries directly into LLM prompts, helping developers get accurate answers without outdated or hallucinated information.
Updated a day ago (2026-09-04 19:06 UTC)
2
879,513
61,623
MIT
Grounded Code MCP
RAG Systems Knowledge & Memory
michaelalber
A
license
Not graded
quality
B
maintenance
A local MCP server that gives AI coding assistants retrieval access to your personal knowledge base of books, standards, and docs, grounding their answers in sources you trust.
Updated 2 months ago (2026-07-14 03:40 UTC)
MIT
docpilot-mcp
Developer Tools Documentation Access
neromtoobad
A
license
Not graded
quality
C
maintenance
An MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.
Updated 3 months ago (2026-06-17 10:03 UTC)
21
ISC
octopilot-mcpofficial
CI/CD & DevOps Developer Tools
octopilot
F
license
A
quality
D
maintenance
Model Context Protocol (MCP) server for Octopilot — enables AI agents to detect, generate, build, and wire up new repositories end-to-end using the Octopilot CI/CD toolchain.
Updated 7 months ago (2026-02-20 07:15 UTC)
7
-

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/utensils/mcp-nixos'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

MCP-NixOS - Because Your AI Shouldn't Hallucinate Package Names

Quick Start

Option 1: uvx (Recommended)

Option 2: Nix

Option 3: Docker

Option 4: HTTP (Remote MCP)

Option 5: Pi Coding Agent

What Is This?

The Tools

nix - Unified Query Tool

nix_versions - Package Version History

Installation

Declarative Installation (NixOS / Home Manager / nix-darwin)

Development

Acknowledgments

License

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Context7 MCP

Grounded Code MCP

docpilot-mcp

octopilot-mcpofficial

Appeared in Searches

Latest Blog Posts

MCP directory API

`nix` - Unified Query Tool

`nix_versions` - Package Version History