Skip to main content
Glama
Sign In
JEFF7712

nix-agent

by JEFF7712
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nix-agent

No user-submitted related servers found.

    Related Servers

    • local-code-mcp

      jutlyne
      F
      license
      Not graded
      quality
      C
      maintenance
      A security-first MCP server that enables clients to inspect and edit multiple local repositories via configured aliases, with read-only Git access and allowlisted test commands.
      4
      -

    • whatbox-mcp

      SNSEIxAUGMNTD
      A
      license
      A
      quality
      D
      maintenance
      A security-first MCP server for managing Whatbox slots with structured read-only inspection and approval-gated mutations, including storage, services, website deployment, and torrent control.
      30
      MIT

    • agentinator

      ESS-ROOT-DIR
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Local-first MCP server for repo-scoped development tasks like inspection, testing, documentation, and patching, designed to complement Cline with a structured local execution layer.
      -

    • local-mcp-toolbox

      chriswayneh
      A
      license
      A
      quality
      A
      maintenance
      A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a mostly distinct role in the Nix lifecycle: build, check, diff, switch, rollback/list generations, eval_config, and locate_option. Some overlap exists around building/validating closures (build vs. check dry-build vs. diff), but the descriptions clarify when each should be used.

    Naming Consistency4/5

    Names are all lowercase snake_case and mostly action-oriented verbs, with multi-word tools following a verb_noun pattern. The main deviation is 'generations', a noun, but the overall convention is predictable and readable.

    Tool Count5/5

    Seven tools is well-scoped for a Nix deployment agent. Each tool covers a meaningful operation, and there is no obvious filler or redundant surface.

    Completeness4/5

    The surface covers the core lifecycle: validation, build, diff, activation, rollback, generation listing, config evaluation, and option location. Direct config file editing/search is not included, but locate_option plus external discovery/editing tools make that a minor gap rather than a dead end.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources