Skip to main content
mcpSource-backed

MCP-NixOS

MCP server for live NixOS, nixpkgs, Home Manager, nix-darwin, Nixvim, FlakeHub, Noogle, NixOS Wiki, nix.dev, NixHub, binary cache, and local flake input lookups.

by James Brink · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/utensils/mcp-nixos/blob/main/README.md, https://github.com/utensils/mcp-nixos
Brand
MCP-NixOS
Brand domain
github.com
Safety notes
MCP-NixOS is primarily a lookup server, but some actions can run local `nix` commands for flake-input inspection when Nix is installed., Package, option, channel, cache, and version results can change as upstream Nix data changes., Binary cache and version history answers are evidence for configuration work, not proof that a deployment or rebuild is safe., Local flake-input and store actions can list or read files under Nix store paths, subject to size and path validation in the source., Verify generated Nix expressions, overlays, and configuration changes with normal Nix evaluation and review before applying them.
Privacy notes
Queries can reveal package names, configuration options, channel choices, flake names, binary cache interests, and local flake dependency structure., Local flake-input reads can expose pinned inputs, paths, and files from Nix store derivations to the MCP client and model provider., Public APIs such as search.nixos.org, FlakeHub, NixHub, Noogle, NixOS Wiki, nix.dev, cache.nixos.org, and GitHub may receive request metadata., Avoid asking the server to read local store files that contain sensitive generated material or private dependency context.
Author
James Brink
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime2Network & hosting110 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 6 risk areas. Review closely: network access, third-party handling.

6 areas
  • SafetyExecution & processesMCP-NixOS is primarily a lookup server, but some actions can run local `nix` commands for flake-input inspection when Nix is installed.
  • SafetyData retentionPackage, option, channel, cache, and version results can change as upstream Nix data changes.
  • SafetyData retentionBinary cache and version history answers are evidence for configuration work, not proof that a deployment or rebuild is safe.
  • SafetyLocal filesLocal flake-input and store actions can list or read files under Nix store paths, subject to size and path validation in the source.
  • SafetyGeneralVerify generated Nix expressions, overlays, and configuration changes with normal Nix evaluation and review before applying them.
  • PrivacyData retentionQueries can reveal package names, configuration options, channel choices, flake names, binary cache interests, and local flake dependency structure.
  • PrivacyThird-party handlingLocal flake-input reads can expose pinned inputs, paths, and files from Nix store derivations to the MCP client and model provider.
  • PrivacyNetwork accessPublic APIs such as search.nixos.org, FlakeHub, NixHub, Noogle, NixOS Wiki, nix.dev, cache.nixos.org, and GitHub may receive request metadata.
  • PrivacyLocal filesAvoid asking the server to read local store files that contain sensitive generated material or private dependency context.

Safety notes

  • MCP-NixOS is primarily a lookup server, but some actions can run local `nix` commands for flake-input inspection when Nix is installed.
  • Package, option, channel, cache, and version results can change as upstream Nix data changes.
  • Binary cache and version history answers are evidence for configuration work, not proof that a deployment or rebuild is safe.
  • Local flake-input and store actions can list or read files under Nix store paths, subject to size and path validation in the source.
  • Verify generated Nix expressions, overlays, and configuration changes with normal Nix evaluation and review before applying them.

Privacy notes

  • Queries can reveal package names, configuration options, channel choices, flake names, binary cache interests, and local flake dependency structure.
  • Local flake-input reads can expose pinned inputs, paths, and files from Nix store derivations to the MCP client and model provider.
  • Public APIs such as search.nixos.org, FlakeHub, NixHub, Noogle, NixOS Wiki, nix.dev, cache.nixos.org, and GitHub may receive request metadata.
  • Avoid asking the server to read local store files that contain sensitive generated material or private dependency context.

Prerequisites

  • Python 3.11 or newer when installing through uvx or pip.
  • Network access to the NixOS, NixHub, FlakeHub, Noogle, wiki, nix.dev, cache, and related APIs used by selected queries.
  • Optional local Nix installation when using local flake-input or Nix-store reading workflows.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "nixos": {
      "command": "uvx",
      "args": ["mcp-nixos"]
    }
  }
}

About this resource

Content

MCP-NixOS is a Model Context Protocol server for giving Claude current Nix and NixOS ecosystem data. It exposes a compact two-tool surface for searching and reading NixOS packages, options, programs, channels, Home Manager options, nix-darwin options, Nixvim options, flakes, FlakeHub records, Noogle functions, NixOS Wiki pages, nix.dev docs, NixHub package metadata, binary cache status, and local flake inputs.

It is designed to reduce hallucinated package names, stale option paths, and outdated Nix channel assumptions. It works without Nix for remote API lookups, while local flake-input and Nix-store actions require Nix and local path access.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, PyPI metadata, Python package metadata, Nix flake, server source, configuration constants, flake-input source, and license file for current setup, supported sources, tool behavior, network use, and licensing.

Features

  • Python package mcp-nixos.
  • Stdio MCP server launched with uvx mcp-nixos, pip install mcp-nixos, or Nix.
  • Unified nix tool for search, info, stats, browse, channels, flake-inputs, cache, and store actions.
  • nix_versions tool for package version history, nixpkgs commit hashes, attribute paths, and platform availability through NixHub data.
  • NixOS packages, options, programs, and channel queries.
  • Home Manager, nix-darwin, Nixvim, FlakeHub, Noogle, NixOS Wiki, nix.dev, NixHub, and binary cache lookups.
  • Optional local flake-input listing, directory listing, and file reading.
  • MIT license.

Installation

Configure the stdio server in your MCP client:

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

After restarting the MCP client, ask Claude to query MCP-NixOS before recommending Nix packages, options, channels, flakes, binary cache status, or version-specific nixpkgs commits.

Use Cases

  • Verify whether a package exists in a NixOS channel.
  • Search NixOS, Home Manager, nix-darwin, or Nixvim options.
  • Find package version history and the nixpkgs commit that shipped a version.
  • Check binary cache availability before planning a build.
  • Search Noogle for Nix function documentation.
  • Read NixOS Wiki or nix.dev material through MCP.
  • Inspect local flake inputs and pinned store paths when Nix is installed.

Safety and Privacy

MCP-NixOS helps with current Nix ecosystem facts, but it should not be treated as a deployment authority. Always evaluate generated Nix expressions, review configuration changes, and test rebuilds with the normal Nix workflow.

Most lookups call public APIs. Local flake-input and store actions can also run Nix commands, list Nix store paths, and read validated store files. Those queries can expose package choices, configuration interests, pinned dependency structure, and local path context to the MCP client and model provider.

Duplicate Check

Existing MCP content includes general developer tools and package-related servers, but no dedicated entry for utensils/mcp-nixos or the mcp-nixos PyPI package was found in content/mcp. This entry is distinct because it covers current NixOS, nixpkgs, Home Manager, nix-darwin, Nixvim, FlakeHub, Noogle, NixOS Wiki, nix.dev, NixHub, binary cache, and local flake-input data.

Source citations

Add this badge to your README

Show that MCP-NixOS is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/mcp-nixos.svg)](https://heyclau.de/entry/mcp/mcp-nixos)

How it compares

MCP-NixOS side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

MCP server for live NixOS, nixpkgs, Home Manager, nix-darwin, Nixvim, FlakeHub, Noogle, NixOS Wiki, nix.dev, NixHub, binary cache, and local flake input lookups.

Open dossier

MCP server that lets Claude install other MCP servers into Claude Desktop by writing MCP config entries for npm packages, uvx packages, or locally cloned Node-based MCP server projects.

Open dossier

MCP server for AI-assisted development task planning, decomposition, dependency tracking, execution workflow state, reflection, and research mode.

Open dossier

Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAgentset logoAgentset
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorJames BrinkAnais Bettscjo4m06Agentset
Added2026-06-062026-06-062026-06-052026-06-06
Platforms
Harness
Source repo
Safety notesMCP-NixOS is primarily a lookup server, but some actions can run local `nix` commands for flake-input inspection when Nix is installed. Package, option, channel, cache, and version results can change as upstream Nix data changes. Binary cache and version history answers are evidence for configuration work, not proof that a deployment or rebuild is safe. Local flake-input and store actions can list or read files under Nix store paths, subject to size and path validation in the source. Verify generated Nix expressions, overlays, and configuration changes with normal Nix evaluation and review before applying them.MCP Installer can write or update Claude Desktop MCP server configuration entries. The install_repo_mcp_server tool can add npx or uvx based MCP server commands from package names the model supplies. The install_local_mcp_server tool can run npm install in a local project with a package.json and configure Node to execute discovered package bins or main files. Environment variables passed to the installer are written into the MCP configuration for the installed server. Treat this as an administrative helper; review every package, version, local path, arg, and environment value before approving a tool call.Shrimp Task Manager persists task plans, project rules, research notes, task status, dependencies, and execution history in `DATA_DIR`. Tools such as `execute_task`, `complete_task`, `delete_task`, `clear_all_tasks`, and `update_task` can change workflow state and should be reviewed before treating status as authoritative. Agent-assignment and planning features can make generated work look more complete than it is; require human review before accepting implementation progress. The optional GUI starts a web interface when enabled; keep it local or protect it with appropriate network controls. Avoid launching development agents with broad permission-bypass flags solely because an example command suggests it.The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
Privacy notesQueries can reveal package names, configuration options, channel choices, flake names, binary cache interests, and local flake dependency structure. Local flake-input reads can expose pinned inputs, paths, and files from Nix store derivations to the MCP client and model provider. Public APIs such as search.nixos.org, FlakeHub, NixHub, Noogle, NixOS Wiki, nix.dev, cache.nixos.org, and GitHub may receive request metadata. Avoid asking the server to read local store files that contain sensitive generated material or private dependency context.MCP configuration files can contain API keys, tokens, local paths, package names, arguments, and environment variables. The server reads and writes the user's Claude Desktop MCP config and may reveal existing MCP server names or config structure through tool results or logs. Local project paths can reveal usernames, repository names, client names, or private workspace layout. Do not ask the installer to write real secrets until you understand where the MCP client stores them and who can read the config file.Task descriptions, project rules, research notes, dependency graphs, agent assignments, prompts, and execution history may include private implementation details. Persisted task data and backups can reveal roadmap items, security work, customer requests, or internal architecture decisions. Tool arguments and task records may be visible to the MCP client and model provider during planning and execution. Review `DATA_DIR` before committing, sharing, archiving, or uploading generated task state.Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Prerequisites
  • Python 3.11 or newer when installing through uvx or pip.
  • Network access to the NixOS, NixHub, FlakeHub, Noogle, wiki, nix.dev, cache, and related APIs used by selected queries.
  • Optional local Nix installation when using local flake-input or Nix-store reading workflows.
  • Claude Desktop or another MCP client that can run stdio Node MCP servers.
  • Node.js and npx available for npm-hosted MCP servers.
  • uvx available before installing Python MCP servers through the uvx path.
  • Package names, local paths, args, and environment variables reviewed before asking Claude to install anything.
  • Node.js 18 or newer and npm available to the MCP client runtime.
  • A cloned, installed, and built checkout of `mcp-shrimp-task-manager`, or an installed package that exposes the built server.
  • A writable `DATA_DIR` for persistent task data and backups.
  • Agreement on how generated plans, task status, agent assignments, and research notes should be reviewed.
  • Agentset account or self-hosted Agentset deployment with a populated namespace.
  • Agentset API key with access to the namespace Claude should query.
  • Node.js 18.17 or newer for running the `@agentset/mcp` package.
  • Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Install
uvx mcp-nixos
Run `npx @anaisbetts/mcp-installer` from Claude Desktop after reviewing the server source and package behavior.
npm install -g mcp-shrimp-task-manager
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.
Config
{
  "mcpServers": {
    "nixos": {
      "command": "uvx",
      "args": ["mcp-nixos"],
      "env": {
        "MCP_NIXOS_TRANSPORT": "stdio"
      }
    }
  }
}
{
  "mcpServers": {
    "mcp-installer": {
      "command": "npx",
      "args": ["@anaisbetts/mcp-installer"]
    }
  }
}
{
  "mcpServers": {
    "shrimp-task-manager": {
      "command": "node",
      "args": ["PATH_TO_SHRIMP_TASK_MANAGER/dist/index.js"],
      "env": {
        "DATA_DIR": "WRITABLE_SHRIMP_DATA_DIR",
        "TEMPLATES_USE": "en",
        "ENABLE_GUI": "false"
      }
    }
  }
}
{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": ["-y", "@agentset/mcp@latest", "--ns", "ns_xxx"],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.