Hetzner Cloud (unofficial)
Typed tools for the Hetzner Cloud API, with read-only, confirm and deny switches
- Pricing
- Open source
- Platforms
- CLI
- Runs
- Locally
- Version
- 0.2.0
- Listing updated
- today
Similar MCP servers
About Hetzner Cloud (unofficial)
Hetzner Cloud (unofficial) is an open-source MCP server for cloud and infrastructure. It runs locally on your machine and is started by your AI client.
Rather than a few hand-picked commands, this server generates one typed tool per operation in Hetzner's Cloud API specification, then adds tuned wrappers for common server tasks. Cloud DNS zones and record sets are covered; Hetzner Robot, the standalone DNS product and Storage Boxes are not.
The server can do exactly what your API token allows, so the safeguards matter. HETZNER_READ_ONLY blocks every write, HETZNER_CONFIRM_WRITES returns a preview unless the call carries a confirm value, and HETZNER_DENY_TOOLS blocks tools by name pattern. Because hcloud_raw_request can reach any endpoint, it should be denied too if you deny others. Requests have capped 429 backoff, automatic pagination and action polling with a time budget.
It is unofficial and unaffiliated with Hetzner, maintained by one person on a best-effort basis. The README warns against versions below 0.2.0, which had a path-injection flaw.
Install
Run in a terminal
claude mcp add the-real-hetzner-mcp --env HETZNER_API_TOKEN='<HETZNER_API_TOKEN>' -- npx -y @mguttmann/hetzner-cloud-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"the-real-hetzner-mcp": {
"command": "npx",
"args": [
"-y",
"@mguttmann/hetzner-cloud-mcp"
],
"env": {
"HETZNER_API_TOKEN": "<HETZNER_API_TOKEN>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"the-real-hetzner-mcp": {
"command": "npx",
"args": [
"-y",
"@mguttmann/hetzner-cloud-mcp"
],
"env": {
"HETZNER_API_TOKEN": "<HETZNER_API_TOKEN>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"the-real-hetzner-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mguttmann/hetzner-cloud-mcp"
],
"env": {
"HETZNER_API_TOKEN": "<HETZNER_API_TOKEN>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"the-real-hetzner-mcp": {
"command": "npx",
"args": [
"-y",
"@mguttmann/hetzner-cloud-mcp"
],
"env": {
"HETZNER_API_TOKEN": "<HETZNER_API_TOKEN>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"the-real-hetzner-mcp": {
"command": "npx",
"args": [
"-y",
"@mguttmann/hetzner-cloud-mcp"
],
"env": {
"HETZNER_API_TOKEN": "<HETZNER_API_TOKEN>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
HETZNER_API_TOKENHetzner Cloud API token from the Cloud Console (project > Security > API tokens). The server can do exactly what this token allows; use a Read token if the client only needs to read.RequiredHETZNER_READ_ONLYtrue: every tool that is not read-only, and hcloud_raw_request with a method other than GET, returns an error without sending a request. Any value other than true, 1, yes, false, 0, no or empty stops the server at startup.HETZNER_CONFIRM_WRITEStrue: every tool that is not read-only returns a preview unless the call carries confirm "YES". Friction against mistakes, not a security boundary.HETZNER_DENY_TOOLSComma-separated tool name globs (for example hcloud_delete_*,hcloud_raw_request) that always return an error. Deny hcloud_raw_request as well, otherwise denied endpoints stay reachable through it. A pattern that matches no tool stops the server at startup.LOG_LEVELLog level of the JSON logs on stderr.
Tools this server provides (1)
Taken from the project documentation; the running server may differ.
- hcloud_raw_request
- Sends a request to any Hetzner Cloud API endpoint.
What it does
- Full API coverage
- One generated tool per Cloud API operation, read and write.
- Read-only switch
- Optionally blocks every tool that changes anything.
- Write confirmation
- Optionally returns a preview until a call carries confirmation.
- Deny patterns
- Blocks tools by name glob.
- Raw request tool
- Escape hatch for any endpoint.
- Resilient calls
- Capped backoff on rate limits, pagination and action polling.
Good for
- List and inspect servers in a Hetzner project
- Create or resize a server from chat
- Manage Cloud DNS records
- Give a team read-only infrastructure visibility
Pricing
Open source
MIT licence; Hetzner's API spec is not covered by it
Hetzner Cloud (unofficial) FAQ
Is it official?
No. It is unaffiliated with Hetzner and its README says so.
How do I keep it from changing anything?
Set HETZNER_READ_ONLY=true, or use a read-only API token.
Which versions should I avoid?
0.1.x. The README says they have a path-injection vulnerability fixed in 0.2.0.
What does it need?
Node.js 22.12 or newer and a Hetzner Cloud API token.
Is Hetzner Cloud (unofficial) free?
Yes. Hetzner Cloud (unofficial) is open source, so you can use and self-host it for free.
How do I add Hetzner Cloud (unofficial) to Claude Code?
Run this command in your terminal: claude mcp add the-real-hetzner-mcp --env HETZNER_API_TOKEN='<HETZNER_API_TOKEN>' -- npx -y @mguttmann/hetzner-cloud-mcp
What are the best alternatives to Hetzner Cloud (unofficial)?
The closest alternatives to Hetzner Cloud (unofficial) are mcp, Webflow, Ripe Stat, Vercel MCP and OpenWrt MCP.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

