Hetzner DNS MCP

Purpose: Managing Hetzner DNS zones and records programmatically through an MCP-compatible interface.

Inferred · not functionally tested

Audience: developers and DevOps engineers

Inferred · not functionally tested

Functions: agents, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: WEB · deployment: browser, self_hosted, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

Hetzner DNS MCP sits in PulseGate's API design, testing & docs category. Inferred · not functionally tested: It focuses on managing Hetzner DNS zones and records programmatically through an MCP-compatible interface. Inferred · not functionally tested: Hetzner DNS MCP is an open-source project aimed at developers and DevOps engineers. Basis unknown · not verified: Hetzner DNS MCP is open source under the Open Source license. Basis unknown · not verified: Hetzner DNS MCP is available on the web, the command line, and API, and it can be self-hosted.

It is developed by ni-c. Inferred · not functionally tested: Among its 5 catalogued features are zone management, record management, and Hetzner API access. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.