HydraDNS MCP Server

io.github.hydradns/hydra-mcp

Repository Registry

What is the HydraDNS MCP server?

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

How to install HydraDNS

Copy-paste configuration for popular MCP clients.

transport: stdio

Config generated by PluginBench — verify against the source before use.

Environment / auth

HYDRA_API_URL
required
Base URL of the HydraDNS controlplane API. Inside a container, 'localhost' means the container itself, not the host running the controlplane. On Docker Desktop (Mac/Windows) the default below resolves automatically. On plain Docker Engine (Linux) either run the container with --add-host=host.docker.internal:host-gateway, or use --network host with http://localhost:8080 instead. Full instructions: docs/mcp.md in the repo, 'Running it -> As the container image'.
HYDRA_TOKEN
required
secret
Bearer token for the HydraDNS API, obtained via `hydra login` or the setup wizard. Grants whatever access the token's account has; MCP_ROLE narrows what the MCP tool layer will call, not what the token itself can do against the API directly.
MCP_ROLE
Permission scope for this MCP session: admin (default, every tool), operator (every mutating tool except toggle_engine), or reporter (read-only tools only). Any unrecognized value safe-defaults to reporter.

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "hydra-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/hydradns/hydra-cli:0.1.0",
        "mcp"
      ],
      "env": {
        "HYDRA_API_URL": "<YOUR_HYDRA_API_URL>",
        "HYDRA_TOKEN": "<YOUR_HYDRA_TOKEN>",
        "MCP_ROLE": "<YOUR_MCP_ROLE>"
      }
    }
  }
}