F
licenseNot graded
qualityC
maintenanceMCP server for managing PowerDNS DNS records through the PowerDNS-Admin API. Supports listing zones, getting zone details, and creating, updating, deleting DNS records.
1
-
mcp-hetzner-dns
by ni-c
Related Servers
Alternatives to mcp-hetzner-dns
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for managing and analyzing Cloudflare DNS — zones, records, analytics, and DNSSEC.141-
- AlicenseBqualityAmaintenanceMCP server for the Hetzner Cloud API. Manage servers, networks, volumes, firewalls, load balancers, and more through the Model Context Protocol.185161 npm4Functional Source , Version 1.1, MIT Future
- AlicenseAqualityCmaintenanceMCP server for the Porkbun DNS API. Manage DNS records, domains, DNSSEC, SSL certificates, and more.2555 PyPI23MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Cloudflare DNS across multiple zones from a single API token, enabling bulk operations like toggling proxy, listing records, and batch updates.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Hetzner. Enables managing cloud projects, account resources, and dedicated servers, with the entire REST API reachable through a searchable tool catalog.1MIT
TDQS
A4.2/5.0
Scored across 22 tools
Disambiguation5/5
Every tool names a specific resource (zone, RRSet, zone action, zonefile) and action (list/get/create/update/delete/change/export/import/set/add/remove). The few overlapping operations like create_rrset vs add_records are explicitly differentiated in their descriptions, so an agent can reliably select the intended tool.
Naming Consistency5/5
Names consistently follow a verb_noun pattern: list_zones, get_zone, create_zone, delete_rrset, change_zone_ttl, set_records, etc. Resource type is always the object and the verb always comes first, with no style mixing. This makes the API highly predictable.
Tool Count4/5
At 22 tools, the server is on the heavy side of the ideal range, but the count is appropriate for the Hetzner DNS API because it covers zones, RRSets, record mutations, zone files, protection, and async actions. The tools are organized into clear groups and each one performs a distinct operation, so the size feels comprehensive rather than redundant.
Completeness5/5
The surface covers the full DNS lifecycle: zone CRUD, import/export, TTL/protection/nameserver changes, RRSet CRUD, record-level add/set/remove, and action status. There are no obvious dead ends—destructive operations have confirmation tokens, and add_records/remove_records handle edge cases like creating or deleting RRSets implicitly.
Maintenance
ActivityActive
ResponsivenessNo issues