Nix MCP Servers

Created By
aloshy-aia year ago
A nix flake for configuring Model Context Protocol (MCP) servers across supported AI assistant clients
Overview

What is nix-mcp-servers?

nix-mcp-servers is a Nix flake designed for configuring Model Context Protocol (MCP) servers across supported AI assistant clients on macOS.

How to use nix-mcp-servers?

To use nix-mcp-servers, add it to your flake.nix file and configure the desired MCP servers (GitHub, GitLab, or Filesystem) with the necessary access tokens and options.

Key features of nix-mcp-servers?

  • Automated configuration of MCP servers for AI assistant clients.
  • Platform-aware client support (macOS only).
  • Supports multiple MCP server types: GitHub, GitLab, and Filesystem.
  • Runtime path validation and permissions checking.
  • Automatic config file management for supported clients.

Use cases of nix-mcp-servers?

  1. Configuring GitHub MCP server for AI assistants.
  2. Setting up GitLab MCP server for self-hosted instances.
  3. Managing filesystem access for AI assistant clients.

FAQ from nix-mcp-servers?

  • Is nix-mcp-servers compatible with other operating systems?

No, it is currently designed for macOS only.

  • How do I configure the GitHub server?

You need to enable it in your configuration and provide a personal access token.

  • Can I use multiple servers at once?

Yes, you can configure multiple servers simultaneously in your setup.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aloshy-ai
Star
0
Language
Nix
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago