Skip to main content
Glama
aolmosj

pz-nitrado-mcp

by aolmosj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pz-nitrado-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-exaroton

      ferronicardoso
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing Exaroton game servers via natural language, enabling server lifecycle control, file management, player lists, and configuration editing.
      -

    • mcp-tailscale

      aplaceforallmystuff
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for managing and monitoring Tailscale networks through natural language. It enables users to list devices, check connection status, monitor for client updates, and retrieve detailed tailnet summaries.
      6
      8 npm
      7
      MIT

    • Discord MCP Server

      shawtymarco
      A
      license
      Not graded
      quality
      D
      maintenance
      A Dockerized MCP server that enables Discord integration, offering tools for role management, messaging, moderation, and server administration via natural language.
      1
      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.3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: service listing, live status, config file discovery, file operations, settings parsing, mod management, log tailing, config profile snapshots, sandbox editing, and lifecycle control. Overlaps like pz_read_file vs pz_get_settings are explicitly disambiguated in descriptions.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern with a pz_ prefix, but two account-level tools use a nitrado_ prefix, creating a minor deviation. The prefix distinction is intentional and logical, but the mixed prefixes prevent a perfect 5.

    Tool Count4/5

    At 20 tools, the server is slightly above the typical 3-15 well-scoped range, but each tool serves a distinct purpose in managing both the Nitrado account and the Project Zomboid server. The breadth is justified by the dual scope (account-level and server-level), so it's only slightly heavy.

    Completeness5/5

    The tool surface covers the full lifecycle of a PZ server: discovery, status, configuration (raw, parsed, and sandbox), mods, logs, config history, and restart/stop. Missing features like a separate start tool are unnecessary because restart serves that role, and the ability to read/write any file fills gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources