HydraDNS

Manage a self-hosted HydraDNS DNS firewall from an assistant: block domains, create policies, and read query logs and metrics.

What you can do

Block and manage domains on the DNS firewall, including toggling the engine on or off depending on role permissions (toggle_engine is admin-only). Create and manage blocking policies. Read query logs and metrics from the controlplane. The tool layer is scoped by MCP_ROLE: admin (default, every tool), operator (all mutating tools except toggle_engine), or reporter (read-only tools only).

When to use it

Useful when you run a self-hosted HydraDNS controlplane and want an assistant to inspect DNS query activity, adjust blocking policies, or block domains without using the CLI directly. Read-only use is possible with the reporter role.

Requirements

Runs locally over stdio, typically as the ghcr.io/hydradns/hydra-cli container via Docker. Needs HYDRA_API_URL pointing at the HydraDNS controlplane API and a HYDRA_TOKEN bearer token obtained via hydra login or the setup wizard. Inside a container, localhost refers to the container, not the host, so the API URL must be reachable from it. MCP_ROLE is optional.