Hetzner README

The full upstream README, mirrored for reference. Install config, tool schemas, adoption signals and our own overview live on the Hetzner listing page.

Hetzner MCP Server

Manage Hetzner Cloud servers, networks, storage, DNS and load balancers from an MCP client. Requires Node.js 22.12 or newer.

Setup

Create an API token in the Hetzner Cloud Console. Use a read-only token for inspection; write operations can create billable resources.

For Claude Code:

Terminal
claude mcp add --env HETZNER_API_TOKEN=your-token --transport stdio \
  hetzner -- npx -y @lazyants/hetzner-mcp-server

For Claude Desktop and clients that accept mcpServers JSON:

config.json
{
  "mcpServers": {
    "hetzner": {
      "command": "npx",
      "args": ["-y", "@lazyants/hetzner-mcp-server"],
      "env": { "HETZNER_API_TOKEN": "your-token" }
    }
  }
}

For a separate Storage Box token, also set HETZNER_STORAGE_API_TOKEN. Otherwise, Storage Box tools use HETZNER_API_TOKEN.

Smaller servers

The default command exposes all tools. To load only one resource group, run a split command:

Terminal
npx -y -p @lazyants/hetzner-mcp-server hetzner-mcp-networking

In a client configuration, replace args with:

json
["-y", "-p", "@lazyants/hetzner-mcp-server", "hetzner-mcp-networking"]

Other groups: servers, load-balancers, ips, storage, storage-boxes, config and dns. Use the same hetzner-mcp- command prefix and token configuration.

Every server exposes the API reference at reference://hetzner/api. See CHANGELOG.md for release changes.

Releasing

Maintainer instructions: release guide.

License

FSL-1.1-MIT. Versions 1.1.1 and earlier remain MIT-licensed.