PluginBench
MCP Server
Active
Apache-2.0

HydraDNS MCP Server

io.github.hydradns/hydra-mcp

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

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
JSON config
{
  "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>"
      }
    }
  }
}

Related MCP servers

Unofficial MCP server for reading and managing Cloudcraft architecture blueprints

0
Python
MIT
View repository →

Unified MCP for 28 static site generators across 19 languages: Zola, Hakyll, and more

View repository →
DODocker MCP Server logo

Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.

0
TypeScript
MIT
View repository →

Modern SSH for AI agents — cloud servers to BusyBox routers, with destructive commands blocked.

1
TypeScript
MIT
View repository →

Convert PDF/CSV to Markdown with AI-powered OCR via the PromptReady cloud API.

0
Python
View repository →

Query Hydrolix data warehouses directly from Claude with SQL execution and metadata tools.

11
Python
Apache-2.0
View repository →