Skip to main content
Glama

Related Servers

Alternatives to hetzner-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage Hetzner Cloud resources including servers, load balancers, and volumes through natural language commands. It facilitates infrastructure operations such as resource creation, security configuration, and real-time pricing queries within AI-powered environments.
      44 npm
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Model Context Protocol server for full Hetzner Cloud + Storage API automation. Exposes all official Hetzner operations as MCP tools so AI agents can manage servers, networking, load balancers, firewalls, volumes, DNS zones, and storage boxes from one server.
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Manage AWS, Hetzner, OVH, and custom SSH servers from AI agents — commands, logs, CloudWatch/CloudTrail, IP banning, and S3, with guard tiers and a full audit trail.
      69
      1,058 PyPI
      29
      MIT

    TDQS

    B3.1/5.0

    Scored across 59 tools

    Disambiguation4/5

    Each named tool targets a distinct resource+action (list/create/delete/attach per resource), so most are easy to tell apart. The three generic *_request tools overlap with every specific tool, creating a dual path an agent must reason about, but their descriptions clearly frame them as fallbacks for missing endpoints.

    Naming Consistency4/5

    The dominant pattern is product_verb_noun (cloud_create_server, robot_list_ips, storagebox_list_types), which is predictable and readable. A handful of infra utilities (infra_map, spend_history, find_capacity, contribute_or_report) break the convention, but this is a minor deviation rather than chaos.

    Tool Count2/5

    59 tools is very heavy for this server and well past the 25-tool threshold, inflated by exhaustive list coverage across cloud/robot/storagebox plus three catch-all request tools that partly duplicate the named tools. The domain is large, but the surface is clearly oversized.

    Completeness4/5

    Coverage is broad: list for nearly every resource plus create/delete for servers, volumes, networks, firewalls, load balancers, IPs, keys, and placement groups. Some lifecycle gaps exist (no server start/stop/reboot, no volume resize, no update/edit tools), but the generic *_request tools provide a usable escape hatch so agents are not stranded.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow