Skip to main content
Glama
lazyants
by lazyants

Related Servers

Alternatives to hetzner-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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
      C
      quality
      D
      maintenance
      A Model Context Protocol server for the Hetzner Cloud API that enables natural language management of cloud infrastructure. Users can list, create, and modify servers, networks, volumes, and load balancers through MCP-compatible clients.
      67
      374 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that allows language models to manage Hetzner Cloud resources through structured functions, including servers, volumes, firewalls, and SSH keys.
      30
      148
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for managing Hetzner DNS zones and RRSets via the Hetzner Cloud API. It enables listing, creating, updating, deleting, importing/exporting zone files, and managing protection and TTLs from MCP clients.
      22
      79 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Open-source MCP server for managing Hetzner Cloud infrastructure with two management layers: * Layer 1 — Hetzner Cloud API (35 tools): Server power control, metrics, snapshots, backups, firewalls, DNS zones and records, rescue mode, server rebuild and rescale. Works even when the server OS is unresponsive. * Layer 2 — SSH (25 tools): Service management (systemd), Nginx config and reload,
      MIT

    TDQS

    B3.4/5.0

    Scored across 185 tools

    Disambiguation4/5

    Most tools are clearly scoped to a resource and action, and descriptions distinguish metadata updates from dedicated lifecycle actions. However, with 185 tools there are many near-pairs across resources (e.g. update_zone vs update_zone_rrset, update_volume vs resize_volume, change_*_protection variants), so some misselection risk remains.

    Naming Consistency4/5

    The set largely follows a predictable hetzner_verb_resource pattern with consistent prefixes and clear action verbs. Minor deviations include mixed load balancer abbreviations (lb vs load_balancer), resource-less server power tools like power_on/reboot/reset/shutdown, and update_* vs change_* usage.

    Tool Count1/5

    185 tools is far beyond a manageable tool surface for an agent, even for a broad cloud provider API. The functionality spans many resources, but this volume creates heavy selection and context overhead rather than a well-scoped set.

    Completeness5/5

    The surface is exceptionally comprehensive, covering CRUD and lifecycle operations for servers, networks, firewalls, load balancers, volumes, images, DNS zones/RRSets, Storage Boxes, IPs, certificates, and placement groups. Actions, metrics, protection, snapshots, and zonefile import/export are also included, leaving few obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow