# MCP-NixOS — Real NixOS Packages for AI Tools (2026)

> mcp-nixos is an MCP server for real NixOS packages/options; verified 638★ with uvx/Docker/Nix configs and optional HTTP mode at `/mcp`.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
uvx mcp-nixos
# or: pip install mcp-nixos && MCP_NIXOS_TRANSPORT=stdio mcp-nixos
# Optional HTTP: MCP_NIXOS_TRANSPORT=http MCP_NIXOS_PORT=8000 mcp-nixos
```

## Intro

mcp-nixos is an MCP server for real NixOS packages/options; verified 638★ with uvx/Docker/Nix configs and optional HTTP mode at `/mcp`.

**Best for:** Teams using agents to generate Nix/NixOS configs and wanting to eliminate hallucinated package names

**Works with:** Claude/Cursor MCP clients, uvx (recommended), Docker/Nix (optional), and remote HTTP MCP endpoints

**Setup time:** 2-5 minutes

## Main

- The README is explicit about the goal: stop agents from inventing package names by giving them a server that queries real NixOS data sources in real time.
- It documents multiple deployment paths (uvx, Nix flake, Docker, remote HTTP), which makes it usable across dev laptops and CI without requiring NixOS itself.
- HTTP mode is first-class: you can run with `MCP_NIXOS_TRANSPORT=http` and serve the MCP endpoint (default `/mcp`), which fits hosted-agent setups.
- A good verification prompt is to ask for a package + option pair and have the agent cite the exact attribute names returned by the server before writing configuration.

### FAQ

- **Do I need NixOS installed?**: No. The README highlights that you are querying APIs, so it can work on Windows/macOS/Linux without running NixOS locally.
- **Which install path should I pick?**: Use the uvx config first; switch to Docker or Nix if you need a pinned runtime or you are deploying to servers.
- **How do I know it is working?**: After adding the MCP server config, ask your client to list tools/resources and verify the NixOS queries return concrete attribute names.

## Source & Thanks

> Source: https://github.com/utensils/mcp-nixos
> License: MIT
> GitHub stars: 638 · forks: 33

---

<!-- ZH -->

## Quick Use

```bash
uvx mcp-nixos
# or: pip install mcp-nixos && MCP_NIXOS_TRANSPORT=stdio mcp-nixos
# Optional HTTP: MCP_NIXOS_TRANSPORT=http MCP_NIXOS_PORT=8000 mcp-nixos
```

## Intro

mcp-nixos 是查询真实 NixOS packages/options 的 MCP server；已核验 638★，提供 uvx/Docker/Nix 配置，并支持 `/mcp` HTTP 模式。

**Best for:** 用 agent 生成 Nix/NixOS 配置、想避免“包名幻觉”的团队

**Works with:** Claude/Cursor 等 MCP 客户端、uvx（推荐）、可选 Docker/Nix，以及远程 HTTP MCP endpoint

**Setup time:** 2-5 minutes

## Main

- README 把目标说得很清楚：通过查询真实数据源来阻止 agent 编造 NixOS 包名，从根上减少配置幻觉。
- 它提供 uvx/Nix/Docker/远程 HTTP 等多种部署方式，甚至强调“不需要 Nix/NixOS 也能用”，更适合团队混合环境。
- HTTP 模式是一等公民：设置 `MCP_NIXOS_TRANSPORT=http` 后就能以默认 `/mcp` 提供服务，适合自托管或远程 agent 场景。
- 推荐的验证方式是：先让 agent 用 server 返回的准确 attribute 名称再写配置，避免“看起来对但其实不存在”的选项。

### FAQ

- **必须装 NixOS 吗？**：不需要。README 强调你是在查询 API，因此 Windows/macOS/Linux 都可以用，不要求本地跑 NixOS。
- **推荐用哪种安装方式？**：优先用 uvx 配置；如果你需要更可控的运行时或部署到服务器，再考虑 Docker 或 Nix。
- **怎么确认配置生效？**：加好 MCP server 配置并重启客户端后，先让它列出工具/资源，再跑一次查询看是否返回具体 attribute 名称。

## Source & Thanks

> Source: https://github.com/utensils/mcp-nixos
> License: MIT
> GitHub stars: 638 · forks: 33


---
Source: https://tokrepo.com/en/workflows/mcp-nixos-real-nixos-packages-for-ai-tools-2026
Author: MCP Hub