mcp-nixos
Related Servers
Alternatives to mcp-nixos
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server that gives AI assistants direct access to live AVEVA PI System documentation, eliminating hallucination on PI-specific topics.3MIT
- AlicenseNot gradedqualityDmaintenanceAn 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.MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol (MCP) server that gives AI assistants full visibility and control over Kubernetes clusters.73MIT

octopilot-mcpofficial
FlicenseAqualityDmaintenanceModel 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.7-- AlicenseNot gradedqualityCmaintenanceA 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.MIT
- AlicenseAqualityBmaintenanceA 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.265,122MIT
TDQS
Scored across 2 tools
The two tools have mostly distinct roles: nix_versions is explicitly for package version history, while nix is the general query tool for everything else. Some ambiguity remains because nix also has an 'info' action that returns package version details, but the description explicitly redirects version history to nix_versions.
nix_versions uses a descriptive snake_case noun pattern, while nix is a bare domain noun. There is no consistent verb_noun pattern across the set, but both names are readable and not chaotic.
Only two tools exist for a very broad Nix ecosystem query surface, and the single nix tool packs dozens of intents into one action-based mega-tool. This is borderline thin and may reduce discoverability, though it keeps the tool list compact.
The surface covers package search and info, channels, options across NixOS/Home Manager/Darwin/Nixvim/NVF, flakes, store paths, binary cache, wiki, nix.dev, and version history. Minor gaps exist, such as an explicit Noogle intent mapping and broader flake metadata operations, but core read-only workflows are well covered.