Slyke/mcp-technitium-dns

Safety-focused MCP server for querying and managing Technitium DNS Server through the Technitium HTTP API.

About mcp-technitium-dns

Safety-focused MCP server for querying and managing Technitium DNS Server through the Technitium HTTP API. Codex or other MCP clients authenticate to this server with named Bearer tokens; this server authenticates to Technitium with a Technitium API token in the Authorization: Bearer ... header. Technitium credentials are never exposed to MCP clients.

Record tools use strict, validated snakecase inputs and map them to Technitium API parameters. For example, an A record uses record: { ipaddress: "192.0.2.10", ttl: 3600 }; an MX record uses record: { preference: 10, exchange: "mail.example.com" }.

Zone export uses Technitium's required GET endpoint with a single-use API token created immediately before export.

READONLY=true registers only read-only tools. Write tools require a readwrite MCP bearer token, and destructive tools require confirm: true.

Target: Technitium DNS Server with API-token based automation.

- Use HTTPS for Technitium whenever possible. - If Technitium is only available over HTTP, set TECHNITIUMALLOWHTTPLOCAL=true; the target host must still be local/private unless it is explicitly listed in TECHNITIUMALLOWHTTPHOSTNAMES. - Create a dedicated Technitium user for MCP automation. - Grant only the permissions needed for your intended tools. - Store the Technitium API token in a protected file and use TECHNITIUMAPITOKENFILE for production deployments. - Set READONLY=true when the server should expose only read-only MCP tools.

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/Slyke--mcp-technitium-dns.html)

Related MCP servers