Technitium MCP

A small tool that lets Claude read and change a Technitium DNS Server through its API.

It runs on your own computer. Your token stays on your computer.

What Claude can do with it

• Look at stats, settings, zones, logs, and users.

• Turn ad blocking on, off, or pause it.

• Flush the cache and refresh block lists.

• Change settings and zones.

• List, add and delete DNS records (technitium_records).

• Test a lookup (technitium_resolve).

• Work with several Technitium servers from one tool (see below).

• Anything else in the Technitium API. 137 endpoints are in the catalog.

Related MCP server: MCP Cloudflare DNS Server

Safety

Every call has a safety level.

• read: runs right away.

• change: does not run until Claude asks you and sets confirm.

• destructive: deleting, restoring, importing, password changes, disabling users, and changing ports or listeners. It also needs the exact endpoint path typed back.

Other protections:

• Login and create-token calls are blocked. They would put a password in the chat.

• The token is never printed. It is removed from error messages.

• File downloads (backups, logs) are saved to a folder. They are not sent to chat. Default folder: technitium-downloads in your home folder.

Set up

1. Make an API token

1. Open the Technitium web page.

2. Go to the Administration part, then Sessions, then create an API token. Menu names can differ a little by version.

3. Best: make a separate user just for this, and make the token from that user. Then you can delete it on its own later.

4. Give the token a name, like Claude.

Do not paste the token in a chat. Put it only in the config file below. If it ever lands in a chat, delete that token and make a new one.

2. Add the tool to Claude

Open the Claude desktop app settings and find the MCP servers config file. Add the block from claude_desktop_config.example.json. Change the address and token.

• TECHNITIUM_URL: your server, like http://192.168.1.10:5380

• TECHNITIUM_TOKEN: your token

That file now holds a secret. Do not share it. Do not put it on GitHub.

The example uses uvx. If you do not have it, use Python instead:

pip install D:\GitHub-Projects\technitium-mcp

Then use "command": "technitium-mcp" and no args.

Restart the Claude desktop app.

3. Try it

Ask Claude: "Show my Technitium stats for the last day."

Several servers in one tool

You can keep one server on its own entry (like ha-blue) and put a group of servers in a second entry. Both entries use the same code.

Example: a cluster with tech-master as the primary and two followers. See claude_desktop_config.example.json for the full block.

• TECHNITIUM_SERVERS: the names, separated by commas.

• TECHNITIUM_URL_<NAME> and TECHNITIUM_TOKEN_<NAME>: one pair per server. <NAME> is the name in capitals, with every other character turned into _. technitium-01 becomes TECHNITIUM_URL_TECHNITIUM_01.

• TECHNITIUM_PRIMARY: the cluster primary. Changes on any other server get a warning that cluster-wide changes belong on the primary.

• Do not set plain TECHNITIUM_URL or TECHNITIUM_TOKEN in a group entry. They are ignored there, so one server's token can never go to another server.

How Claude uses it:

• Every tool has a server option. In a group, Claude must give a name.

• technitium_servers lists the names, addresses and the primary. No tokens.

• server: "all" works for read-only calls only. Good for comparing stats, settings or a lookup across all servers.

• Changes and deletes need exactly one server name. No "all".

• Each server needs its own API token. A bad token breaks only that server.

If TECHNITIUM_SERVERS is not set, the tool works as before with one server.

Note: in technitium_resolve, the old server option (which DNS server to ask) is now dns_server. server now means which Technitium server runs the lookup.

Other settings

• TECHNITIUM_VERIFY_TLS=false: for an https address with a self-signed certificate.

• TECHNITIUM_TOKEN_IN_QUERY=true: for an old Technitium version that ignores the Bearer header. This puts the token in the URL, so avoid it if you can.

• TECHNITIUM_DOWNLOAD_DIR: where downloads are saved.

• TECHNITIUM_VERIFY_TLS_<NAME>: same as above, for one server in a group.

Test it

pip install mcp
python tests/test_server.py
python tests/test_multi.py

The tests start fake Technitium servers and check every tool and every safety rule. test_multi.py checks the several-server mode with three fake servers.

Limits

• File uploads are not supported yet: zone import, settings restore, and app install from a file. Installing an app from a URL works.

• Cluster options are in the catalog but not tested.

• Tested against a fake server only. Not yet tested on a real one.

Credits

Endpoint list built from the official Technitium API docs. Technitium is made by Technitium. This project is not made by Technitium.

License

MIT. See LICENSE.