hetzner-mcp
Related Servers
Alternatives to hetzner-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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 npm1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents like Mistral Work to manage Hetzner Cloud VPS services in natural Spanish, including creating, modifying, and deleting servers, networks, firewalls, and storage, as well as automating complex tasks.MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to manage and monitor Hetzner Cloud infrastructure, including servers, firewalls, networks, and snapshots, while keeping the API token local and secure.MIT
- AlicenseBqualityDmaintenanceEnables conversational management of Hetzner Cloud, DNS, and Storage Box infrastructure through 137 MCP tools for CRUD operations and actions like server power control, DNS zone management, and storage box snapshots.100MIT
- AlicenseNot gradedqualityAmaintenanceModel 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.1MIT
- AlicenseBqualityAmaintenanceManage 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.691,058 PyPI29MIT
TDQS
Scored across 59 tools
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.
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.
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.
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.