MCP-NixOS MCP Server
MCP-NixOS bridges AI assistants with the NixOS ecosystem, offering programmatic access to configuration, package management, and system state for robust automation.

What does “MCP-NixOS” MCP Server do?
MCP-NixOS is a Model Context Protocol (MCP) Server specifically designed to interface with NixOS resources. It acts as a bridge between AI assistants and the NixOS ecosystem, enabling seamless access to NixOS configuration, package management, and system state. By exposing NixOS data and operations through the MCP standard, MCP-NixOS empowers developers and AI systems to query, manage, and interact with NixOS environments programmatically. This facilitates workflows such as automated system configuration, package discovery, and state introspection—making it highly valuable for infrastructure automation, reproducible builds, and AI-powered DevOps tasks.
List of Prompts
No prompt templates were found in the repository or its documentation.
List of Resources
No explicit MCP resources were documented or found in the repository structure or documentation.
List of Tools
No explicit tools were found in the server.py or equivalent implementation files in the repository.
Use Cases of this MCP Server
- NixOS Configuration Exploration
Developers and AI systems can introspect NixOS configurations, making it easier to understand system setups and automate documentation. - Automated Package Management
The server can be used to query and manage NixOS packages, streamlining development and deployment pipelines. - System State Introspection
Enables real-time querying of current system state, useful for monitoring, troubleshooting, and self-healing infrastructure. - Declarative Infrastructure Automation
Facilitates AI-driven updates or validation of declarative system configurations, ensuring consistency and reproducibility. - Integration with LLM-based DevOps Agents
AI agents can leverage MCP-NixOS to perform actions or gather context, enhancing their ability to assist with NixOS-based workflows.
How to set it up
Windsurf
- Ensure you have Node.js and Windsurf installed.
- Open your Windsurf configuration file.
- Add the MCP-NixOS server entry to the
mcpServers
section. - Save the configuration and restart Windsurf.
- Verify the setup by running a test query via the UI.
{
"mcpServers": {
"mcp-nixos": {
"command": "npx",
"args": ["@utensils/mcp-nixos@latest"]
}
}
}
Claude
- Install Node.js and Claude if not already present.
- Locate Claude’s configuration file.
- Insert the MCP-NixOS server details under the
mcpServers
key. - Save changes and restart Claude.
- Confirm the server is accessible from Claude’s interface.
{
"mcpServers": {
"mcp-nixos": {
"command": "npx",
"args": ["@utensils/mcp-nixos@latest"]
}
}
}
Cursor
- Make sure Cursor and Node.js are installed.
- Edit the Cursor configuration file.
- Add MCP-NixOS in the
mcpServers
section. - Save the config and restart Cursor.
- Use Cursor’s interface to test connectivity.
{
"mcpServers": {
"mcp-nixos": {
"command": "npx",
"args": ["@utensils/mcp-nixos@latest"]
}
}
}
Cline
- Install Node.js and Cline.
- Open Cline’s main config file.
- Add MCP-NixOS to the
mcpServers
array. - Save and restart Cline.
- Run a basic MCP command to verify the integration.
{
"mcpServers": {
"mcp-nixos": {
"command": "npx",
"args": ["@utensils/mcp-nixos@latest"]
}
}
}
Note:
To secure API keys or sensitive environment variables, use the env
field in your configuration. Example:
{
"mcpServers": {
"mcp-nixos": {
"command": "npx",
"args": ["@utensils/mcp-nixos@latest"],
"env": {
"API_KEY": "${API_KEY}"
},
"inputs": {
"apiKey": "${API_KEY}"
}
}
}
}
How to use this MCP inside flows
Using MCP in FlowHunt
To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:
{
"mcp-nixos": {
"transport": "streamable_http",
"url": "https://yourmcpserver.example/pathtothemcp/url"
}
}
Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “mcp-nixos” to your actual MCP server name and replace the URL with your own MCP server URL.
Overview
Section | Availability | Details/Notes |
---|---|---|
Overview | ✅ | |
List of Prompts | ⛔ | None documented |
List of Resources | ⛔ | None found |
List of Tools | ⛔ | None found |
Securing API Keys | ✅ | env field in config |
Sampling Support (less important in evaluation) | ⛔ | Not documented |
I would rate this MCP server as a 5/10: it has strong documentation for setup and use cases, but lacks explicit prompt templates, resources, and tools in the current repository state.
MCP Score
Has a LICENSE | ✅ (MIT) |
---|---|
Has at least one tool | ⛔ |
Number of Forks | 10 |
Number of Stars | 142 |
Frequently asked questions
- What is MCP-NixOS?
MCP-NixOS is a Model Context Protocol server for NixOS, allowing AI assistants and developers to programmatically access, manage, and introspect NixOS configurations, packages, and system state for automation and DevOps workflows.
- What are common use cases for MCP-NixOS?
Typical use cases include NixOS configuration exploration, automated package management, real-time system state introspection, declarative infrastructure automation, and integration with LLM-based DevOps agents.
- Does MCP-NixOS provide prompt templates or explicit resources?
No, the current version does not include prompt templates or explicit documented resources or tools, but it exposes NixOS data and operations via the MCP standard.
- How do I secure API keys or sensitive variables?
Use the `env` field in your configuration file to securely store and reference sensitive environment variables like API keys when setting up MCP-NixOS.
- What is the license for MCP-NixOS?
MCP-NixOS is released under the MIT License.
- How do I integrate MCP-NixOS into a FlowHunt workflow?
Add the MCP component to your flow in FlowHunt, then insert your MCP-NixOS server details in the configuration panel using the recommended JSON format to enable AI agents to access its capabilities.
Try MCP-NixOS with FlowHunt
Empower your DevOps and automation workflows by integrating MCP-NixOS with FlowHunt for seamless NixOS management.