Skip to content

hetzner-dns-mcpYour DNS, through the assistant

An MCP server for the Hetzner Cloud DNS API — 22 tools for zones, record sets, zone files, TTLs and protection, with a confirmation token in front of everything irreversible.

The two-step flow, in 15 seconds

Listing the tools, a refused set_records call, and the same call succeeding with the confirmation token it returned

How it fits together

Architecture of hetzner-dns-mcpAn MCP client speaks JSON-RPC over stdio to hetzner-dns-mcp, which validates arguments, gates destructive calls behind a confirmation token, and calls the Hetzner Cloud API over HTTPS. Responses pass back through a sanitizer.MCP clientClaude Code, Desktop,Codex, Inspectorhetzner-dns-mcpzod schemas · path guardsconfirmation tokensredact · truncate · markHetzner Cloudapi.hetzner.cloud/v1/zonesstdioresultsHTTPSJSON
Arguments are validated before they reach a URL; results are sanitized before they reach the model.

In one command

bash
claude mcp add hetzner-dns -s user \
  -e HETZNER_API_TOKEN=your-token \
  -- npx -y hetzner-dns-mcp

Then ask for what you want — "what does the www record for example.com point at?", "add an AAAA record for the new host", "export the zone file before we touch anything". See Getting started for the token, and Connecting clients for Claude Desktop, Codex, the Inspector and Docker.

Released under the MIT License.