HydraDNS

Name: HydraDNS
Author: hydradns

本地服务

github.com安全15 周前更新

代码仓库访问官网

关于 HydraDNS

管理可自托管的 DNS 防火墙：屏蔽域名、创建策略、读取查询日志和指标。

配置

本地服务的配置在各客户端中通用，复制后粘贴到客户端的 MCP 配置文件即可。

mcp.json · 通用配置

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

启动命令docker run -i --rm -e HYDRA_API_URL -e HYDRA_TOKEN -e MCP_ROLE ghcr.io/hydradns/hydra-cli:0.1.0

需要配置的环境变量

HYDRA_API_URLBase 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密钥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_ROLEPermission 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.

本地服务需要在你的电脑上安装运行环境（如 Node.js 18+）。各客户端的配置文件位置不同，请参考客户端文档。

安装包

ocighcr.io/hydradns/hydra-cli:0.1.0stdio