hetzner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSH_KEY | No | SSH key used by the host module (alternative to SSH_KEY_PATH). | |
| HOSTS_FILE | No | Path to the host registry (config/hosts.json) that bounds which hosts SSH can reach. | |
| HCLOUD_TOKEN | No | Hetzner Cloud API token. Switches on the cloud module (and can contribute to the dns module and recipes for new servers). | |
| SSH_KEY_PATH | No | Path to the SSH key used by the host module (alternative to SSH_KEY). | |
| COOLIFY_BASE_URL | No | Coolify base URL. Together with COOLIFY_API_TOKEN switches on the coolify module. | |
| COOLIFY_API_TOKEN | No | Coolify API token. Together with COOLIFY_BASE_URL switches on the coolify module. | |
| PROTECTED_SERVERS | No | List of servers that are protected; destructive calls on them are refused even with confirm. | |
| CLOUDFLARE_API_TOKEN | No | Cloudflare API token. Switches on the dns module (together with HCLOUD_TOKEN). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Operates a Hetzner estate: Cloud servers, DNS, hosts over SSH, Coolify. Start with hz_fleet_overview or hz_capabilities. Every write tool returns a dry-run plan unless confirm=true: show the plan to the user and only confirm after they agree. Destructive calls on protected resources are refused.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hz_fleet_overviewA | Every server in every configured Hetzner project: status, type, location, IP, backups, volumes, gross €/month, registry name and role, protection. Volume and traffic costs are not included in the total. |
| hz_host_listC | The host registry: SSH targets, roles, protection, allowed paths, Caddy. |
| hz_host_registerA | Add a host to the registry (or replace its entry). Only registered hosts are reachable over SSH. Set protected=true on the mail server. test_ssh checks the login before saving. Safety: dry run unless confirm=true. |
| hz_host_removeA | Remove a host entry. The server itself is untouched; SSH tools can no longer reach it. Safety: dry run unless confirm=true; refused on protected resources. |
| audit_logB | Most recent calls through this MCP, newest first: tool, mode (read/dry_run/execute/refused), result, summary. |
| hz_capabilitiesB | Which modules are on, what they point at, and what to configure to switch the others on. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct job: registry listing, registration, removal, fleet inventory, audit history, and capability reporting. The only mild overlap is hz_host_list vs hz_fleet_overview (registry SSH targets vs Hetzner cloud servers with costs), but descriptions make the distinction clear enough.
Most tools follow a hz_<resource>_<action> snake_case pattern (hz_host_list, hz_host_register, hz_host_remove, hz_fleet_overview), which is predictable. Deviations are minor: audit_log lacks the hz_ prefix and hz_capabilities is resource-only with no verb.
Six tools is well-scoped for a registry-plus-inventory server; each earns its place (three host CRUD operations, one fleet read, plus two meta/observability tools). Nothing feels redundant or padded.
Registry lifecycle is covered (list/register/replace/remove), but there is no get-single-host detail tool and no Hetzner server lifecycle operations (create, delete, power, resize, snapshots) despite the server's name implying cloud management. hz_capabilities hints modules may be toggled on, so the surface is intentionally partial but has notable gaps.