Nix MCP Servers logo

Nix MCP Servers

by aloshy-ai

A Nix flake for declaratively configuring MCP (Model Context Protocol) servers for clients like Claude and Cursor. It supports multiple server types and clients, providing a unified configuration system across different platforms.

View on GitHub

Last updated: N/A

What is Nix MCP Servers?

Nix MCP Servers is a Nix flake that provides a declarative way to manage Model Context Protocol (MCP) server configurations for AI clients such as Claude and Cursor. It allows you to define and manage configurations for different server types (filesystem, GitHub) in a consistent manner across multiple platforms.

How to use Nix MCP Servers?

To use Nix MCP Servers, add the flake as an input to your Home Manager, NixOS, or nix-darwin configuration. Then, configure the nix-mcp-servers module to enable clients and servers, specifying paths, tokens, and other settings. The flake will generate the necessary configuration files for each client.

Key features of Nix MCP Servers

  • Declarative configuration of MCP servers

  • Support for multiple clients (Claude, Cursor)

  • Support for multiple server types (filesystem, github)

  • Cross-platform support (NixOS, Darwin, Home Manager)

  • Integration with existing Nix configurations

Use cases of Nix MCP Servers

  • Centralized management of MCP server configurations

  • Consistent configuration across different development environments

  • Automated setup of MCP servers for AI clients

  • Simplified configuration for multiple clients and servers

FAQ from Nix MCP Servers

What is MCP?

MCP stands for Model Context Protocol. It's a protocol used by AI clients to access models and data from different sources.

What clients are supported?

Currently, Claude and Cursor are supported.

What server types are supported?

Filesystem and GitHub servers are supported.

How do I configure the GitHub server?

You need to provide a GitHub Personal Access Token (PAT) with appropriate permissions.

How do I test my configuration?

After applying the configuration, you can check the generated configuration files in the client-specific directories.