
Hetzner
io.github.lazyantsPublished by GitHub account lazyantsv4.1.0Updated Nov 14, 2026
MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more.
Overview
MCP server that lets an assistant manage Hetzner Cloud resources — servers, networks, volumes, firewalls, load balancers, IPs, DNS and Storage Boxes — via the…
- What you can do
- Create, inspect and manage Hetzner Cloud servers
- Manage networks, firewalls, volumes and floating IPs
- Manage load balancers and DNS records
- Manage Storage Boxes, optionally with a separate storage token
- Read the bundled Hetzner API reference resource
- Load only one resource group via split commands (servers, networking, load-balancers, ips, storage, storage-boxes, config, dns)
- When to use it
- Useful when you want an assistant to inspect or operate Hetzner Cloud infrastructure from a chat client — checking servers and networks, adjusting firewalls or DNS, or provisioning resources — without switching to the Hetzner console.
- Requirements
- Runs locally over stdio via npx, requiring Node.js 22.12 or newer. Needs a Hetzner Cloud API token in HETZNER_API_TOKEN; a separate Storage Box token can be set in HETZNER_STORAGE_API_TOKEN, otherwise the cloud token is used. Desktop clients only.
Installation
In SourceWeft
- Open Hetzner in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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:
For Claude Desktop and clients that accept mcpServers JSON:
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:
In a client configuration, replace args with:
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.
Source: README.md at commit 6c42fa1
Tools
0Version history
6- v4.1.0LatestNov 14, 2026
- v4.0.3Nov 7, 2026
- v4.0.2Oct 23, 2026
- v3.0.1Oct 3, 2026
- v3.0.0Oct 2, 2026
- v2.5.0Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.