Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hetzner-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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

    • hcloud-mcp

      Xodus-CO
      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
      477 npm
      MIT

    • Hetzner Cloud MCP Server

      dkruyt
      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
      145
      MIT

    • mcp-hetzner-dns

      ni-c
      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
      68 npm
      MIT

    • Hetzner Cloud MCP Server —

      wbf-solutions
      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
    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.3/5.0

    Scored across 185 tools

    Disambiguation3/5

    The tool set is highly systematic but very large; many tools share the same action verb across different resources (e.g., change_*_protection, list_*_actions) and several server power tools (power_off, shutdown, reset, reboot) have subtle distinctions. Descriptions clarify boundaries, but the sheer volume and repeated patterns increase the risk of misselection.

    Naming Consistency4/5

    Names consistently use the hetzner_ prefix and snake_case verb_noun structure (e.g., create_server, delete_volume, list_zones). Minor inconsistencies exist: 'lb' is sometimes abbreviated (get_lb_metrics, list_lb_types) while other tools use 'load_balancer', and power actions are verb-only (power_on, reboot).

    Tool Count1/5

    185 tools is far beyond the recommended 3-15 range and exceeds the 50+ threshold for extreme mismatch, making it impractical for an agent to navigate efficiently despite the API's breadth.

    Completeness5/5

    The surface covers servers, storage boxes, DNS, networking, load balancers, and more with full CRUD and action coverage, including edge operations like rescue mode, console access, zonefile import/export, and snapshot plans. No obvious gaps in lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources