Onlydns MCP logo

Onlydns MCP

Manage OnlyDNS domains, DNS records, DNSSEC settings, and TSIG keys through MCP tools.

Install Onlydns MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "onlydns-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@onlydns/mcp"
      ],
      "env": {
        "ONLYDNS_API_TOKEN": "YOUR_VALUE_HERE",
        "ONLYDNS_API_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

onlydns-mcp MCP server connects MCP-compatible AI clients to the OnlyDNS API for inspecting and changing DNS infrastructure. It supports domain and record management, DNSSEC status and signing controls, and TSIG key administration for zone transfers and dynamic updates. Run it through npx or a global npm installation with an OnlyDNS bearer token, then use it when an agent needs controlled access to DNS zones.

Use cases

  • List domains and inspect their DNS records
  • Create and update DNS zones from an agent workflow
  • Enable or disable DNSSEC signing
  • Generate TSIG keys for zone transfers
  • Configure AXFR and dynamic DNS permissions

Key features

  • Domain listing and zone creation
  • Filtered DNS record queries
  • Individual and batch record changes
  • DNSSEC status and signing controls
  • TSIG key generation and management
  • AXFR and dynamic update permissions

Tools8

What Onlydns MCP lets your agent do. Expand a tool for its parameters.

Self-reported~10 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commitTodayMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Tools exposed8Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Onlydns MCP works

What onlydns-mcp does

onlydns-mcp exposes OnlyDNS account and zone administration through the Model Context Protocol. Agents can enumerate managed domains, create DNS zones, inspect records, and modify individual records or complete record sets. Record operations support filtering by record type or hostname and cover common types such as A, AAAA, CNAME, MX, TXT, SRV, CAA, URL, and PROXY.

The server also provides DNSSEC controls and TSIG key management. Agents can inspect DNSSEC state and retrieve DS or DNSKEY data, enable or disable signing, list and retrieve TSIG keys, generate keys with supported HMAC algorithms, and assign transfer or update permissions to domains.

How it works

The package runs as an MCP process and communicates with the OnlyDNS REST API using a bearer token. A client starts the package with npx -y @onlydns/mcp or invokes a globally installed executable. The default API endpoint is https://api.onlydns.com/v1; deployments can provide a different base URL through configuration.

Domain and record changes are exposed as separate MCP operations. Records can be added, updated, deleted, or replaced in batches. TSIG configuration can permit AXFR transfers, RFC 2136 dynamic updates, and optional restrictions for subdomains.

Setup and configuration

Install the package globally:

Terminal
npm install -g @onlydns/mcp

Alternatively, run it without a permanent installation:

server.ts
export ONLYDNS_API_TOKEN="your_onlydns_api_token"
npx -y @onlydns/mcp

The required ONLYDNS_API_TOKEN value is an OnlyDNS API bearer token. ONLYDNS_API_BASE_URL can override the default REST API base URL. MCP clients that launch commands can register the package with npx, pass -y and @onlydns/mcp as arguments, and provide the token in the process environment.

An MCPB bundle is also available from the project's GitHub Releases page for compatible desktop clients. Claude Desktop can be configured with an mcpServers entry that launches the package and supplies the token.

Tools and capabilities

  • List managed domains with optional pagination and create new DNS zones.
  • Query records by domain, record type, or hostname.
  • Add, append, update, delete, or batch-replace DNS records.
  • Inspect DNSSEC status and retrieve DS and DNSKEY records.
  • Enable or disable DNSSEC signing for a zone.
  • List TSIG keys, retrieve key details, and create keys using algorithms such as hmac-sha256 and hmac-sha512.
  • Read or change domain TSIG permissions, including AXFR, dynamic DNS updates, and optional subdomain limits.

Limitations and notes

DNS changes and security-setting changes require an OnlyDNS bearer token with suitable account permissions. Batch replacement through set_records affects the full record set for a zone, so it should be used with an intentional complete record definition. TSIG configuration controls transfer and update permissions but does not itself perform a zone transfer or dynamic update.

The package is licensed under MIT. Its documented client configurations cover Claude Desktop, Cursor, Windsurf, and Claude Code.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Onlydns MCP

onlydns-mcp is an MCP server that connects AI clients to the OnlyDNS API. Its main tools list domains, create zones, query and modify DNS records, manage DNSSEC signing, and create or configure TSIG keys for AXFR transfers and RFC 2136 dynamic updates.

Install it globally with `npm install -g @onlydns/mcp`, or run it directly with `npx -y @onlydns/mcp`. Set `ONLYDNS_API_TOKEN` to an OnlyDNS bearer token before launching the process.

onlydns-mcp requires `ONLYDNS_API_TOKEN`. You can also set `ONLYDNS_API_BASE_URL` to override the default `https://api.onlydns.com/v1` OnlyDNS API endpoint.

Yes, onlydns-mcp works with Cursor. Add an MCP server entry that launches `npx -y @onlydns/mcp` and provide `ONLYDNS_API_TOKEN` in the entry's environment settings.

Yes, it can inspect, enable, and disable DNSSEC, including retrieving DS and DNSKEY data. It can also list, retrieve, and create TSIG keys and configure domain permissions for AXFR and dynamic DNS updates.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOnlydns MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/onlydns-mcp?style=directory)](https://allmcps.com/mcp/onlydns-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/onlydns-mcp"><img src="https://allmcps.com/api/badge/onlydns-mcp?style=directory" alt="Onlydns MCP on AllMCPs" /></a>