HydraDNS

io.github.hydradns/hydra-mcp · v0.1.0

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

Website Source code Set it up

Connect Runs on your machine

Terminal

claude mcp add hydra-mcp -e HYDRA_API_URL=<HYDRA_API_URL> -e HYDRA_TOKEN=<HYDRA_TOKEN> -e MCP_ROLE=<MCP_ROLE> -- docker run -i --rm ghcr.io/hydradns/hydra-cli:0.1.0

claude_desktop_config.json

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

~/.cursor/mcp.json

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

.vscode/mcp.json

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

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server runs locally, so its tools are listed by your MCP client once it starts.

Environment variables

Name	Description
`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…
`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` Optional	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.

Details

Package	`ghcr.io/hydradns/hydra-cli:0.1.0` (OCI, stdio)
First published	21 Sep 2026
Last updated	21 Sep 2026
Registry name	`io.github.hydradns/hydra-mcp`

More cloud and devops servers See all

Live status

Local install

Installed and run on your own machine, so there is no public endpoint to check.

Pair it with live search

Agents that use HydraDNS often also need current facts. NestDaddy MCP gives your AI today's internet: web search, real-time breaking news and full page reading in one connector.

See NestDaddy MCP

For maintainers

[![NestDaddy MCP](https://nestdaddy.com/mcp/servers/io-github-hydradns-hydra-mcp/badge.svg)](https://nestdaddy.com/mcp/servers/io-github-hydradns-hydra-mcp)

Add the badge to your README. It turns green while your server passes our daily check. Listing details come from the official MCP registry; update them there.

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.