Log inSubmit server
Hetzner logo

Hetzner

Manage Hetzner Cloud servers, networking, storage, IPs, DNS, and load balancers through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Hetzner

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hetzner": {
      "command": "npx",
      "args": [
        "-y",
        "@lazyants/hetzner-mcp-server"
      ],
      "env": {
        "HETZNER_API_TOKEN": "YOUR_VALUE_HERE",
        "HETZNER_STORAGE_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The hetzner MCP server connects AI agents to the Hetzner Cloud API for managing servers, networks, volumes, firewalls, load balancers, IPs, DNS zones, and related resources. It provides 185 tools across 15 resource domains, with separate entry points for reducing the tool set exposed to an MCP client. Actions can be monitored with a shared wait tool, and a read-only API reference resource is available at `reference://hetzner/api`. Use it when an agent needs to inspect or change Hetzner infrastructure through Claude Code, Claude Desktop, or another stdio-capable MCP client.

Use cases

  • Provision and resize Hetzner Cloud servers
  • Configure private networks and firewall rules
  • Manage volumes, images, and server backups
  • Operate load balancers, certificates, and DNS zones
  • Inspect pricing, metrics, locations, and infrastructure actions

Key features

  • 185 tools across 15 Hetzner resource domains
  • Split entry points for smaller tool sets
  • Server, network, storage, IP, DNS, and load balancer management
  • Shared asynchronous action waiting
  • Read-only API reference resource
  • Optional separate Storage Box token

Tools80

What Hetzner lets your agent do. Expand a tool for its parameters.

Self-reported~467 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @lazyants/hetzner-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads1.5kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed80Callable tools this server registers over MCP.

How Hetzner works

What hetzner MCP server does

The hetzner MCP server exposes Hetzner infrastructure operations through the Model Context Protocol. It connects to the Hetzner Cloud API and covers compute, networking, storage, load balancing, certificates, DNS zones, IP addresses, images, ISOs, SSH keys, placement groups, locations, server types, and pricing.

The package contains 185 tools across 15 resource domains. Server tools can create, update, delete, power-cycle, rebuild, resize, protect, monitor, and connect servers to networks or placement groups. Other domains provide comparable read and mutation operations for resources such as volumes, firewalls, floating IPs, primary IPs, load balancers, certificates, and networks.

A read-only API reference resource is exposed at reference://hetzner/api from every entry point. The server also includes hetzner_wait_for_action, which can track operations for supported resource domains until they succeed, fail, or reach a timeout.

How it works

The hetzner MCP server runs as a Node.js package using stdio. The complete command registers all available tools, while split commands expose narrower groups: servers, networking, load balancers, IPs, storage, Storage Boxes, configuration resources, or DNS. Choosing only the required groups can reduce the context and tool count presented to an agent.

Most list operations support sorting. Image queries can filter by the server they belong to and include deprecated images when requested. Metrics for servers and load balancers accept a step size in seconds. Pricing queries can be limited to a resource category, including server types, load balancer types, volumes, IPs, traffic, images, or server backups.

The action-waiting tool accepts a domain, resource ID, action ID, and optional timeout. Its default timeout is 300 seconds and its maximum is 3,600 seconds. It polls resource action history and observes MCP cancellation while waiting.

Setup and configuration

Install the package globally with npm install -g @lazyants/hetzner-mcp-server, or run it directly with npx @lazyants/hetzner-mcp-server. Set HETZNER_API_TOKEN to a token created in the Hetzner Cloud Console under Security and API Tokens.

Storage Box operations use a separate Hetzner API host. They use HETZNER_STORAGE_API_TOKEN when it is set; otherwise, they reuse HETZNER_API_TOKEN. A dedicated storage token is therefore optional rather than required for Storage Box access.

Claude Code and Claude Desktop configurations start the package with npx and pass the token through the client environment. Split commands can be registered separately when only selected resource domains are needed.

Tools and capabilities

  • Manage servers, images, ISOs, volumes, networks, firewalls, and placement groups.
  • Configure load balancers, targets, services, certificates, and public interfaces.
  • Create, assign, unassign, protect, and update floating or primary IPs.
  • Query locations, server types, pricing, metrics, actions, and API reference data.
  • Work with DNS zones and Storage Boxes through their supported entry points.
  • Wait for asynchronous Hetzner actions across supported resource domains.

Limitations and notes

The full entry point exposes 185 tools, which may be too large for clients with strict tool limits; split entry points are available for that reason. Storage Box calls use a separate API host and may require a separately scoped token. Datacenter endpoints are no longer exposed because Hetzner removed them after 2026-10-01; location and server-type tools provide the documented availability information instead.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Hetzner

hetzner is an MCP server that connects AI agents to the Hetzner Cloud API and its Storage Box API. Its main tools manage servers, networks, volumes, firewalls, load balancers, IPs, DNS zones, images, certificates, and related resources, while a shared tool waits for asynchronous Hetzner actions to complete.

Install it with `npm install -g @lazyants/hetzner-mcp-server` or run it directly with `npx @lazyants/hetzner-mcp-server`. Set `HETZNER_API_TOKEN` to a Hetzner Cloud API token, then register the command in your MCP client configuration.

Add the package as an MCP server in `claude_desktop_config.json`, using `npx` with `@lazyants/hetzner-mcp-server` and passing `HETZNER_API_TOKEN` in the `env` object. The README provides a complete configuration example for the full entry point.

Use one or more split entry points instead of the full command. Available groups include servers, networking, load balancers, IPs, storage, Storage Boxes, configuration resources, and DNS, allowing a client to load only the domains it needs.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHetzner AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hetzner?style=directory)](https://allmcps.com/mcp/hetzner)
HTML Embed
<a href="https://allmcps.com/mcp/hetzner"><img src="https://allmcps.com/api/badge/hetzner?style=directory" alt="Hetzner on AllMCPs" /></a>