Technitium DNS MCP server
Commit Nov 1, 2026Lets an AI assistant audit, manage, and configure Technitium DNS servers, including zones, records, DHCP, and DNSSEC settings.
Also known as katbyte/technitium-mcp
- Stars
- 0
- Tools
- 10
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 1, 2026
- License
- GPL-3.0
What is Technitium DNS MCP?
Technitium DNS lets an AI assistant audit, manage, and configure Technitium DNS servers, including zones, records, DHCP, and DNSSEC settings. It exposes 10 tools, such as core, audit, ops.
Summary generated from the project's README
About Technitium DNS MCP server
Managing and auditing Technitium DNS infrastructure is what this MCP server enables for network administrators and developers. It provides an interface for an AI assistant to inspect, troubleshoot, and configure DNS settings, DHCP scopes, and DNSSEC keys across one or multiple servers simultaneously. By using the server with a client like Claude Code, you can perform deep inspections of your network configuration to find discrepancies or security weaknesses.
Setup requires a Technitium DNS Server version 15.0 or newer and an API token generated from the web console. Users configure the connection by specifying the server URL and token in a local configuration file. The system is designed with a safety-first approach where the assistant only performs read operations by default. To modify records or settings, you must explicitly enable write or delete permissions. This ensures that no accidental changes occur during an audit without your direct command.
What you can do with it
- 1Perform comprehensive network auditsAsk the assistant to run a full sweep of all zones and records to identify configuration errors.
- 2Synchronize multiple DNS serversIdentify differences in zones and records between different servers in your cluster.
- 3Manage DHCP and DNS consistencyEnsure that your DHCP scopes and DNS records are in agreement.
Written from the project's README. Every use case is checked against a quote from it.
Technitium DNS MCP tools 10
Detected from the READMEcoreauditopseditblockdhcpdnssecclusteradminapps
Configuration
TECHNITIUM_TOOLSETS
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablekatbyte/technitium-mcp is public and reachablegithub.com/katbyte/technitium-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)GPL-3.0spdx.org/licenses/GPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-01github.com/katbyte/technitium-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubtechnitium-mcp - a Technitium DNS Server MCP server, CLI and Go SDK
Lets an AI assistant read, check and manage Technitium DNS Server. It is an MCP server, a command line and a Go client.
Finding a problem is code. Fixing it is a decision. The audits sweep every zone on every server and return a list of what is wrong, each with its fix. Nothing changes until you turn changes on and a tool is called.
go install github.com/katbyte/technitium-mcp@latest
Make an API token on the server (web console, Administration, Sessions, Create Token) and put it in ~/.technitium-mcp:
SERVER=http://nas:5380
TOKEN=<token>
Register it with Claude Code in .mcp.json:
{ "mcpServers": { "technitium": { "command": "technitium-mcp", "args": ["serve"] } } }
Then ask for audit_all. Needs Technitium DNS Server 15.0 or newer.
What it does
- Works on several servers at once. A read asks every server and shows the answers side by side, so differences stand out.
- Only reads, until told otherwise. Changing needs
--enable-write. Deleting needs--enable-deleteas well. - Shows a change first. Every change takes
dry_run, and reads back what it did afterwards. - Covers the whole server. 106 tools: zones, records, cache, blocking, DHCP, DNSSEC, clusters, accounts, apps, settings, backups and logs.
- Keeps secrets out. No password, token or key is shown in an answer or a log.
The audits
Every audit only reads. The full rules for each are in docs/audits.md.
| audit | what it catches |
|---|---|
audit_all |
Runs the audits below in one pass and gives counts. Start here. |
audit_servers |
Zones and records that differ between servers. Fix with zone_resync or record_set. |
audit_targets |
Records that point at a name and end nowhere. Fix with record_set or record_delete. |
audit_reverse |
Addresses and reverse entries that disagree. Fix with record_set. |
audit_overlaps |
Records never served, and every wildcard. Fix with record_delete. |
audit_naming |
Probable typing slips and odd lifetimes. Fix with record_set. |
audit_state |
What is switched off or set to delete itself. Fix with zone_edit or record_set. |
audit_zones |
Zones whose own records do not name their servers. Fix with zone_edit or record_set. |
audit_security |
What is left open to the network. Fix with settings_set or zone_edit. |
audit_access |
Weak accounts and permissions. Fix with user_set or session_delete. |
audit_cluster |
A cluster that is not whole. Fix with cluster_edit. |
audit_dnssec |
Signing keys that wait on something or are weak. Fix with dnssec_key_edit. |
audit_queries |
Failing forwarders and odd patterns in a day of queries. Fix with settings_set. |
audit_apps |
Apps out of date or not alike across servers. Fix with app_install. |
audit_blocking |
Blocking that is off, empty or uneven. Fix with block_switch or block_lists_set. |
audit_dhcp |
Where DHCP and DNS do not agree. Fix with dhcp_scope_set or dhcp_reservation_set. |
audit_split |
Inside against outside, by asking a resolver you name. Not in audit_all. Fix with record_set. |
audit_names |
Checks a list of host names you give it. Fix with record_set. |
Tools
Tools are named for what they act on, such as zone_list or record_set, and grouped into toolsets. Only core loads by default, to keep a session small.
| toolset | what it is for | tools |
|---|---|---|
core |
See what the servers are and hold. Always loaded. | 7 |
audit |
Find what is wrong. | 17 |
ops |
Settings, statistics, logs and backups. | 17 |
edit |
Change zones and records. | 12 |
block |
What the servers refuse to resolve. | 9 |
dhcp |
Scopes, leases and reservations. | 8 |
dnssec |
Sign zones and manage keys. | 7 |
cluster |
Make, grow, shrink and end a cluster. | 8 |
admin |
Accounts, groups, tokens and permissions. | 16 |
apps |
The DNS apps a server runs. | 5 |
TECHNITIUM_TOOLSETS=audit # find what is wrong
TECHNITIUM_TOOLSETS=edit,dhcp TECHNITIUM_ENABLE_WRITE=true # change records and reservations
More
- docs/tools.md: every tool, choosing which load, and what a change does before it is made.
- docs/configuration.md: every flag and setting, several servers, running over HTTP, and Docker.
- docs/audits.md: what each audit looks for.
- docs/client.md: using the Go client on its own.
- docs/development.md: building, the folders, and how the tests run.
- docs/ROADMAP.md: the design rules, known limits and what is not built.
- api-defs/README.md: where the server differs from its own API document.
- CONTRIBUTING.md: how changes and releases are made.
How this is built
- The code is written with Claude Code. I review it, and prune or rework it until it has the shape I want.
- I set the design, the scope and the audit rules, and decide what stays.
- Every tool and every client method must have a live test against a real Technitium server in Docker. CI fails if one is missing.
- The live tests run three ways: on one server, on two, and on the two joined as a cluster.
- CI also runs unit tests, golangci-lint, CodeQL, govulncheck, a Trivy vulnerability scan of the built binary, and a check that vendored dependencies match.
- Workflows are checked with actionlint, yamllint and zizmor. Scripts are checked with shellcheck, and docs with typos and markdownlint.
Technitium DNS MCP questions
What tools does Technitium DNS MCP provide?
It exposes 10 tools, including core, audit, ops, edit, block.
What version of Technitium DNS Server is required?
You need Technitium DNS Server version 15.0 or newer.
Does the server make changes to my DNS configuration automatically?
No, the server only reads data by default. You must explicitly enable write or delete permissions to make changes.
How do I authenticate with the server?
You must create an API token in the Technitium web console under Administration > Sessions > Create Token and provide it in your configuration.
Can I manage multiple DNS servers at once?
Yes, the server can work on several servers simultaneously and show differences between them side by side.