Domeneshop

[domeneshop-mcp — MCP server for Domeneshop domains, DNS, HTTP forwards, dynamic DNS and invoices]

[CI] [npm version] [npm downloads] [License]

Manage your Domeneshop domains by asking your AI assistant. DNS records, HTTP forwards, dynamic DNS and invoices, all in plain language. Works with Claude, Cursor, VS Code, Codex and any other MCP client.

"Set up email for example.no"
"Point blog.example.no at 203.0.113.10"
"Which of my domains renew this year?"

The assistant picks the right tool, shows you what it is about to change and asks before it does.

Getting started

1. Get an API token and secret from domeneshop.no/admin?view=api.

2. Add the server. With Claude Code:

claude mcp add domeneshop \  --env DOMENESHOP_API_TOKEN=<your-api-token> \  --env DOMENESHOP_API_SECRET=<your-api-secret> \  -- npx -y domeneshop-mcp

Using Claude Desktop, Cursor, VS Code or something else? Pick your client below. Most have a one-click install.

3. Try it. Start a new session and ask "List my Domeneshop domains".

[!TIP] Not ready to let an assistant touch live DNS? Add --env DOMENESHOP_READ_ONLY=true and it can look at everything but change nothing.

Requires Node.js 22 or newer (download), except for the Claude Desktop bundle.

What you can ask for

Client setup

Every client needs the same two environment variables, DOMENESHOP_API_TOKEN and DOMENESHOP_API_SECRET. Most take this standard config. If the file already lists other servers, add the "domeneshop" entry inside the existing "mcpServers" object:

{  "mcpServers": {    "domeneshop": {      "command": "npx",      "args": ["-y", "domeneshop-mcp"],      "env": {        "DOMENESHOP_API_TOKEN": "<your-api-token>",        "DOMENESHOP_API_SECRET": "<your-api-secret>"      }    }  }}

claude mcp add-json domeneshop '{"command":"npx","args":["-y","domeneshop-mcp"],"env":{"DOMENESHOP_API_TOKEN":"<your-api-token>","DOMENESHOP_API_SECRET":"<your-api-secret>"}}'

{  "servers": {    "domeneshop": {      "type": "stdio",      "command": "npx",      "args": ["-y", "domeneshop-mcp"],      "env": {        "DOMENESHOP_API_TOKEN": "<your-api-token>",        "DOMENESHOP_API_SECRET": "<your-api-secret>"      }    }  }}

code --add-mcp '{"name":"domeneshop","command":"npx","args":["-y","domeneshop-mcp"],"env":{"DOMENESHOP_API_TOKEN":"<your-api-token>","DOMENESHOP_API_SECRET":"<your-api-secret>"}}'

[mcp_servers.domeneshop]command = "npx"args = ["-y", "domeneshop-mcp"]env = { DOMENESHOP_API_TOKEN = "<your-api-token>", DOMENESHOP_API_SECRET = "<your-api-secret>" }

brew install martinzachariassen/tap/domeneshop-mcp   # macOS/Linux, installs Node.js if missingnpm install -g domeneshop-mcp                        # or with npm

{  "mcpServers": {    "domeneshop": {      "command": "/opt/homebrew/bin/domeneshop-mcp",      "env": {        "DOMENESHOP_API_TOKEN": "<your-api-token>",        "DOMENESHOP_API_SECRET": "<your-api-secret>"      }    }  }}

Configuration

All settings are environment variables, passed with --env in Claude Code or in the env block of your client config. Only the first two are required.

Tools

17 tools cover every operation the Domeneshop API offers. You don't need to know their names, because the assistant picks them for you. Arguments are validated before anything is sent (TTL range, URL scheme, IP addresses, the fields each record type requires), so a mistake comes back as an explanation, not a bare API error.

[!WARNING] update_dns_record replaces the whole record: omitted fields are dropped and an omitted ttl resets to 3600 seconds. Use patch_dns_record to change only some fields. upsert_dns_record refuses to act when a host has several records of the same type (typical for MX and TXT) and lists their IDs instead.

Safety

[!IMPORTANT] Domeneshop has no scoped tokens: a token can do everything your account can. Limit what the assistant can do by limiting which tools the server exposes.

• Read-only mode: DOMENESHOP_READ_ONLY=true exposes only the eight read-only tools. This is a good default for trying the server out.
• Allowlist: DOMENESHOP_TOOLS=list_domains,list_dns_records,patch_dns_record exposes exactly those tools.
• Denylist: DOMENESHOP_DISABLED_TOOLS=delete_dns_record,delete_forward hides specific tools.

Hidden tools are not registered at all, so the model never sees them. The settings combine, and a misspelled tool name stops the server at startup instead of being silently ignored.

Keep your client's confirmation prompt on for write tools. They change live DNS, and a wrong record can take a site or mailbox offline.

Credentials are only sent to api.domeneshop.no and are never logged. To revoke access, delete the token in the Domeneshop control panel.

Troubleshooting

For more detail, set DOMENESHOP_DEBUG=true. The server then logs every API request (method, path, status and duration, never credentials) to stderr, which most clients show in their MCP logs.

Still stuck? Open an issue.

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md for the development workflow, and the API notes for undocumented Domeneshop behaviour the client relies on. Everyone taking part is expected to follow the Code of Conduct.

Available on npm, Homebrew, the MCP Registry and as a Claude Desktop bundle. To report a vulnerability, see SECURITY.md. Licensed under MIT.