Hetzner Cloud MCP by usefulapi
Server Details
Servers, volumes, networks, firewalls, load balancers, pricing and safe power operations.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 32 tools
Each tool targets a distinct resource+action, and the get vs list pairs (e.g. hetzner_list_certificates vs hetzner_get_certificates) are separable. However, all nine hetzner_get_* resource fetchers share the identical boilerplate description 'Fetch a single resource by id.', so an agent must rely entirely on the noun to disambiguate. Power-on/reboot/shutdown are clearly distinct.
Near-uniform hetzner_verb_noun snake_case with a consistent prefix. Minor deviations: the single-resource fetchers are named inconsistently in plurality (hetzner_get_server/get_action singular vs hetzner_get_certificates/get_volumes plural), and hetzner_poweron_server omits the noun/verb separator used elsewhere (reboot_server, shutdown_server).
32 tools is on the heavy side for the rubric's 25+ threshold, though Hetzner Cloud is a genuinely broad domain (servers, volumes, networks, firewalls, load balancers, IPs, certificates, keys). The count is inflated by eight near-identical read-only get/list pairs, several of which are thin wrappers.
Server lifecycle is well covered (create, get, list, poweron, reboot, shutdown, protection, backups, metrics, snapshot), but there is no server delete/resize/rebuild, and volumes, networks, firewalls, load balancers, floating/primary IPs, certificates and SSH keys expose only list+get with no create/update/delete. This leaves major dead ends for managing anything other than servers.
Related MCP Connectors
Inspect servers, storage, networks, databases and billing, and start, stop or back up servers.
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
Cloud VMs, Secure VMs and GPU VMs: live plans and prices, plan advice, docs, and your servers.
GPU cloud platform — create, manage, and monitor instances, snapshots, SSH keys, and billing.
Related MCP Servers
- FlicenseNot 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.534 npm1-
- AlicenseAqualityCmaintenanceEnables management of LunaNode VPS resources including VMs, images, volumes, floating IPs, SSH keys through natural language with tiered safety controls.12MIT
- AlicenseBqualityAmaintenanceInspect and manage IONOS CLOUD infrastructure via MCP11811Apache 2.0
- AlicenseNot gradedqualityCmaintenanceOpen-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
Glama MCP Gateway
Add one secure layer between your agents and this server.