Nix MCP Servers

What is Nix MCP Servers?

A Nix flake for declaratively configuring Model Context Protocol (MCP) servers for clients like Claude and Cursor. It supports filesystem and GitHub server types and works across NixOS, darwin, and Home Manager.

How to use Nix MCP Servers?

Add the flake to your Nix configuration (NixOS, nix-darwin, or Home Manager), then enable desired servers and clients using module options (e.g., clients.cursor.enable = true). A CLI tool is also provided via nix run github:aloshy-ai/nix-mcp-servers.

Key features of Nix MCP Servers

• Declarative MCP server configuration using Nix
• Support for multiple clients (Claude, Cursor)
• Support for multiple server types (filesystem, GitHub)
• Cross-platform support (NixOS, Darwin)
• Integrates with Home Manager
• Customizable configuration paths per client

Use cases of Nix MCP Servers

• Grant Claude Desktop filesystem access to specific project directories
• Enable GitHub API access for AI coding assistants
• Manage MCP server configurations across Linux and macOS machines
• Version-control team MCP server settings using Nix

FAQ from Nix MCP Servers

What servers are supported?

Filesystem and GitHub servers are supported.

Which clients are supported?

Claude (Anthropic's Claude AI assistant) and Cursor (code editor).

How do I set a custom configuration path?

Override configPath at the module level or per client, e.g., configPath = "/custom/path/to/mcp".

What are the runtime requirements?

Nix (NixOS, nix-darwin, or Home Manager) and appropriate credentials (e.g., a GitHub personal access token).

How can I test my configuration?

Run sudo nixos-rebuild test (NixOS), darwin-rebuild test (nix-darwin), or home-manager switch (Home Manager), then check the generated config file at the client‑specific path (e.g., ~/Library/Application Support/Claude/mcp-config.json).