Manage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics.
HydraDNS is an MCP integration. Manage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics.
The published oci package is ghcr.io/hydradns/hydra-cli:0.1.0. Its declared MCP transport is stdio.
The package declares 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): 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..
This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related monitoring & observability MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| HYDRA_API_URL | 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'. | Yes |
| 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. | Yes |
| 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. | Optional |
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
MCP server and CLI that resolves config/env-var cascade across .env, docker-compose, and Kubernetes
A Model Context Protocol (MCP) server providing tool interfaces for legal information queries, weather data, Azure pricing, and utility functions.
MCP server for Dynadot domain registrar — domain search, registration, DNS, and transfers
A Python server that implements Model Context Protocol(MCP) for Crossplane. It allows LLM to talk to Kubernetes and query Crossplane-related resources, such as, CompositeResourceDefinition(XRD)…