io.github.lazyants/hetzner
MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@lazyants/hetzner-mcp-serverclaude mcp add hetzner -e 'HETZNER_API_TOKEN=<your hetzner_api_token>' -e 'HETZNER_STORAGE_API_TOKEN=<your hetzner_storage_api_token>' -- npx -y @lazyants/hetzner-mcp-server@4.0.2
{
"mcpServers": {
"hetzner": {
"command": "npx",
"args": [
"-y",
"@lazyants/hetzner-mcp-server@4.0.2"
],
"env": {
"HETZNER_API_TOKEN": "<your hetzner_api_token>",
"HETZNER_STORAGE_API_TOKEN": "<your hetzner_storage_api_token>"
}
}
}
}
Environment variables
HETZNER_API_TOKENrequired secret Hetzner Cloud API token.HETZNER_STORAGE_API_TOKENsecret Storage Box API token; falls back to HETZNER_API_TOKEN when omitted.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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:
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:
{
"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:
npx -y -p @lazyants/hetzner-mcp-server hetzner-mcp-networking
In a client configuration, replace args with:
["-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.
Frequently asked questions
What is io.github.lazyants/hetzner?
MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more.
How do I install io.github.lazyants/hetzner?
It runs on your machine. In Claude Code: claude mcp add hetzner -e 'HETZNER_API_TOKEN=<your hetzner_api_token>' -e 'HETZNER_STORAGE_API_TOKEN=<your hetzner_storage_api_token>' -- npx -y @lazyants/hetzner-mcp-server@4.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.lazyants/hetzner need an API key?
Yes. It expects HETZNER_API_TOKEN, HETZNER_STORAGE_API_TOKEN, which you set in its configuration.
Is io.github.lazyants/hetzner open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.lazyants/hetzner?
It is published by lazyants. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.