Skip to main content
Glama
mjmirza

hetzner-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hetzner-mcp

No user-submitted related servers found.

    Related Servers

    • Hetzner MCP

      Xodus-CO
      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.
      59 npm
      1
      -

    • hetzner-mcp

      devinoldenburg
      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

    • Servonaut

      zb-ss
      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
      281 PyPI
      28
      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

    B3.4/5.0

    Scored across 34 tools

    Disambiguation5/5

    Each tool targets a distinct resource or API action using clear prefixes (robot_, cloud_, storagebox_). List tools are uniquely named per resource, and the generic request tools are explicitly separate. No ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent pattern: prefix_verb_noun in snake_case (e.g., robot_list_subnets, cloud_list_servers). Even the utility tool contribute_or_report fits the style. No mixing of conventions.

    Tool Count3/5

    With 34 tools, the count is on the high side for a typical server, but it covers multiple Hetzner APIs (Robot, Cloud, Storage Box). The number is borderline but reflects the broad scope.

    Completeness2/5

    The tool set is heavily read-only with only two mutation tools (server create/delete). Missing CRUD for other resources like networks, firewalls, volumes, load balancers, and any update operations. Generic request tools partially compensate but indicate significant gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources