domeneshop-mcp
Manage Domeneshop domains through 17 tools covering domains, DNS, HTTP forwards, dynamic DNS and invoices.
Domains: list all domains (filterable by name) and get details like expiry, renewal, nameservers and services.
DNS records: list, get, create, fully replace, partially patch, upsert, and delete records across 11 types (A, AAAA, ANAME, CAA, CNAME, DS, MX, NS, SRV, TLSA, TXT).
HTTP forwards: list, get, create, update (destination/frame) and delete host forwards to http/https/ftp URLs.
Dynamic DNS: point one or more hostnames at given or apparent IPv4/IPv6 addresses, creating records if missing.
Invoices: list invoices from the past three years (filter by status) and get a single invoice with a PDF link.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@domeneshop-mcp list my domains and show the DNS records for example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcpUsing 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".
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.
MCP (Model Context Protocol) is an open standard that lets AI apps call outside tools. This package is an MCP server: a small program your AI app starts in the background. You never run it yourself and you do not need to know the tool names. You just ask.
The API token and secret let a program act on your Domeneshop account, so treat them like a password.
Related MCP server: Name.com MCP Server
What you can ask for
Area | Example prompt |
Domains | "Which domains are on my account, and when do they renew?" |
DNS | "Show every DNS record for example.no" |
DNS | "Lower the TTL on the www record for example.no to 5 minutes" |
DNS | "Add the TXT record Google gave me for domain verification" |
Forwarding | "Forward old.example.no to https://example.no" |
Dynamic DNS | "Update home.example.no to my current IP" |
Invoices | "List my unpaid Domeneshop invoices" |
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>"
}
}
}
}Use the command from Getting started. It registers the
server for you in this project only (--scope local). Add --scope user to
make it available in every project, or --scope project to write
<your-project>/.mcp.json and share it through version control.
You can also pass the standard config as raw JSON:
claude mcp add-json domeneshop '{"command":"npx","args":["-y","domeneshop-mcp"],"env":{"DOMENESHOP_API_TOKEN":"<your-api-token>","DOMENESHOP_API_SECRET":"<your-api-secret>"}}'Run /mcp in a session, or claude mcp list, to check that it connects.
Download
domeneshop-mcp-<version>.mcpbfrom the latest release.Open it (double-click, or drag it into Claude Desktop).
Paste your token and secret, optionally turn on read-only mode, and install.
Claude Desktop stores the credentials securely.
To configure it by hand instead, add the standard config to
claude_desktop_config.json (Settings → Developer → Edit Config), then restart
Claude Desktop:
Platform | Full path |
macOS |
|
Windows |
|
Linux (unofficial builds) |
|
The button installs the server with placeholder credentials. Afterwards, open
Settings → MCP, edit the domeneshop entry and replace <your-api-token>
and <your-api-secret> with your own.
To set it up by hand instead, add the standard config to an mcp.json file:
Scope | Full path |
This project only |
|
Every project (macOS/Linux) |
|
Every project (Windows) |
|
The buttons install the server in your user configuration. VS Code then asks for your token and secret and stores them securely, so nothing is written to a config file in plain text.
To set it up by hand instead, note that VS Code uses a servers key instead of
mcpServers and wants an explicit type. For this project only, add it to
<your-project>/.vscode/mcp.json:
{
"servers": {
"domeneshop": {
"type": "stdio",
"command": "npx",
"args": ["-y", "domeneshop-mcp"],
"env": {
"DOMENESHOP_API_TOKEN": "<your-api-token>",
"DOMENESHOP_API_SECRET": "<your-api-secret>"
}
}
}
}For every project, run MCP: Open User Configuration from the command palette and add the same block, or register it in one line:
code --add-mcp '{"name":"domeneshop","command":"npx","args":["-y","domeneshop-mcp"],"env":{"DOMENESHOP_API_TOKEN":"<your-api-token>","DOMENESHOP_API_SECRET":"<your-api-secret>"}}'Add this to ~/.codex/config.toml (%USERPROFILE%\.codex\config.toml on
Windows):
[mcp_servers.domeneshop]
command = "npx"
args = ["-y", "domeneshop-mcp"]
env = { DOMENESHOP_API_TOKEN = "<your-api-token>", DOMENESHOP_API_SECRET = "<your-api-secret>" }codex mcp add domeneshop -- npx -y domeneshop-mcp also works, but takes no
env flags, so set the two variables in the block it creates.
Anything that runs MCP servers over stdio works. Most use the standard config above. Check your client's documentation for the config file and key name, then point it at:
command:
npxargs:
["-y", "domeneshop-mcp"]env:
DOMENESHOP_API_TOKENandDOMENESHOP_API_SECRET
To avoid resolving the package on every launch, install it once and use
domeneshop-mcp as the command with no args:
brew install martinzachariassen/tap/domeneshop-mcp # macOS/Linux, installs Node.js if missing
npm install -g domeneshop-mcp # or with npmIn Claude Code, that means -- domeneshop-mcp in place of
-- npx -y domeneshop-mcp. brew upgrade domeneshop-mcp picks up new releases.
GUI apps such as Claude Desktop usually do not see Homebrew's PATH, so give
them the full path. brew --prefix prints it: /opt/homebrew on Apple
silicon, /usr/local on Intel Macs, /home/linuxbrew/.linuxbrew on Linux.
{
"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.
Variable | Required | Description |
| Yes | API token from the Domeneshop control panel |
| Yes | The matching API secret |
| No |
|
| No | Comma-separated allowlist of tool names to expose |
| No | Comma-separated tool names to hide |
| No | Per-request timeout in milliseconds (default |
| No |
|
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.
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.
Access mirrors the MCP annotations each tool declares, which clients use to decide what to run without asking.
Area | Tool | Access | Description |
Domains |
| Read-only | List all domains on the account, optionally filtered by name |
| Read-only | Get a single domain by its Domeneshop domain ID | |
DNS |
| Read-only | List a domain's records, optionally filtered by host and type |
| Read-only | Get a single record by ID | |
| Adds | Create a record and return it as stored | |
| Overwrites | Replace a whole record (see the warning above) | |
| Overwrites | Change only the given fields of a record | |
| Overwrites | Update the single record for a host and type, or create it if there is none | |
| Deletes | Delete a record | |
Forwarding |
| Read-only | List a domain's HTTP forwards |
| Read-only | Get the forward for one host | |
| Adds | Create a forward to an | |
| Overwrites | Update a forward's destination or frame setting; an omitted | |
| Deletes | Delete a forward | |
Dynamic DNS |
| Overwrites | Point one or more comma-separated hostnames at up to nine IPv4/IPv6 addresses, or at the caller's apparent IP; creates the record if missing |
Invoices |
| Read-only | List invoices from the past three years, optionally filtered by status |
| Read-only | Get a single invoice |
All eleven record types Domeneshop accepts are supported:
Type | Fields beyond |
| — |
|
|
|
|
|
|
|
|
|
|
tag is a number for DS (the key tag, 0-65535) and a string for CAA (the
property tag, such as issue). A and AAAA data must be an address of the
matching family, and the numeric fields are range-checked.
Safety
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=trueexposes 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_recordexposes exactly those tools.Denylist:
DOMENESHOP_DISABLED_TOOLS=delete_dns_record,delete_forwardhides 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
Problem | Fix |
The tools don't show up | Restart the client (most load servers only at startup), or check |
| The token or secret is wrong. Copy both again from domeneshop.no/admin?view=api. Surrounding whitespace is trimmed automatically. |
| The domain or record ID doesn't exist on this account. Ask the assistant to list domains or records first. |
Timeouts | Requests give up after 30 seconds. Idempotent requests are retried on rate limiting and temporary errors. Raise the limit with |
A DNS change doesn't show up | DNS is cached for the record's TTL (3600 seconds by default), so resolvers may serve the old value for up to an hour. Ask the assistant to show the record to confirm Domeneshop stored it. |
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.
Available Tools
17 toolscreate_dns_recordCreate DNS recordB
Create a new DNS record for a domain. Returns the stored record, including its new ID.
Inputs: data (required), host (required), type (required), domain_id (required), +11 more. Returns: id, alg, tag, ttl, +11 more
create_forwardCreate HTTP forwardA
Create a new HTTP forward for a domain. Fails if the host already has a forward or a conflicting A, AAAA, ANAME or CNAME record.
Inputs: url (required), host (required), domain_id (required), frame. Returns: url, host, frame
delete_dns_recordDelete DNS recordBDestructiveIdempotent
Delete a DNS record. This cannot be undone.
Inputs: domain_id (required), record_id (required).
delete_forwardDelete HTTP forwardBDestructiveIdempotent
Delete an HTTP forward. This cannot be undone.
Inputs: host (required), domain_id (required).
get_dns_recordGet DNS recordBRead-onlyIdempotent
Get a single DNS record by ID.
Inputs: domain_id (required), record_id (required). Returns: id, alg, tag, ttl, +11 more
get_domainGet domainARead-onlyIdempotent
Get details for a single domain by its Domeneshop domain ID: expiry, renewal, nameservers and active services.
Inputs: domain_id (required). Returns: id, renew, domain, status, +5 more
get_forwardGet HTTP forwardBRead-onlyIdempotent
Get the HTTP forward configured for a specific host.
Inputs: host (required), domain_id (required). Returns: url, host, frame
get_invoiceGet invoiceARead-onlyIdempotent
Get details for a single invoice, including a link to the PDF.
Inputs: invoice_id (required). Returns: id, url, type, amount, +5 more
list_dns_recordsList DNS recordsBRead-onlyIdempotent
List DNS records for a domain, optionally filtered by host and/or record type.
Inputs: domain_id (required), host, type. Returns: records
list_domainsList domainsARead-onlyIdempotent
List all domains on the Domeneshop account, optionally filtered by domain name. Use this first to find the domain_id the other tools need.
Inputs: filter. Returns: domains
list_forwardsList HTTP forwardsARead-onlyIdempotent
List all HTTP forwards configured for a domain.
Inputs: domain_id (required). Returns: forwards
list_invoicesList invoicesARead-onlyIdempotent
List invoices from the past three years on the Domeneshop account, optionally filtered by status.
Inputs: status. Returns: invoices
patch_dns_recordPatch DNS recordADestructiveIdempotent
Change only some fields of an existing DNS record, e.g. just data or ttl. The current record is read first and every field you leave out keeps its stored value; when you change the type, give the new type's required fields too. Prefer this over update_dns_record. Returns the stored record.
Inputs: domain_id (required), record_id (required), alg, tag, +12 more. Returns: id, alg, tag, ttl, +11 more
update_dns_recordReplace DNS recordADestructiveIdempotent
Replace an existing DNS record. This overwrites the whole record, so send every field it should keep: any omitted field is dropped, and leaving out ttl resets it to the default 3600 seconds. To change only some fields, use patch_dns_record instead. Returns the stored record.
Inputs: data (required), host (required), type (required), domain_id (required), +12 more. Returns: id, alg, tag, ttl, +11 more
update_dyndnsUpdate dynamic DNSADestructiveIdempotent
Point one or more hostnames at the given (or the caller's apparent) IP address using Domeneshop's dynamic DNS protocol. The record type (A or AAAA) follows from the address; a missing record is created, an existing one overwritten.
Inputs: hostname (required), myip.
update_forwardUpdate HTTP forwardADestructiveIdempotent
Update an existing HTTP forward for a domain. Returns the stored forward. frame keeps its stored value unless given. The host itself cannot be changed: to move a forward, delete it and create it again for the new host.
Inputs: url (required), host (required), domain_id (required), frame. Returns: url, host, frame
upsert_dns_recordCreate or update DNS recordADestructiveIdempotent
Make sure a host has exactly this record of the given type: updates the existing record for that host and type, or creates one if there is none. When updating, optional fields you leave out (e.g. ttl, priority) keep their stored value. Fails without changing anything if the host already has several records of that type (common for MX and TXT); then use patch_dns_record with a record_id, or create_dns_record to add another. Returns { action: "created" | "updated", record }.
Inputs: data (required), host (required), type (required), domain_id (required), +11 more. Returns: action, record
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Resources are cleanly partitioned (domains, DNS records, HTTP forwards, invoices) and the four DNS write tools (create/update/patch/upsert) are explicitly differentiated, including a cross-reference telling the agent to prefer patch_dns_record. The only residual risk is that update/upsert/patch all mutate a record and an agent could pick wrong, but the descriptions genuinely resolve this.
Every tool follows the same snake_case verb_noun pattern (list_domains, get_dns_record, create_forward, patch_dns_record, update_dyndns). The verb set is small and applied predictably across all four sub-resources.
17 tools across four sub-domains (2 domain, 7 DNS, 5 forward, 2 invoice) is proportionally balanced and each tool covers a distinct operation. It sits just outside the ideal 3-15 band and the four DNS mutation tools add some redundancy.
DNS records and HTTP forwards both have full CRUD plus partial-update and upsert, and domains/invoices are readable with useful filters. Gaps are minor and likely intentional: no domain settings/nameserver update or domain deletion, and invoices are read-only, but the core workflows are all reachable.
Maintenance
Related MCP Connectors
Register, transfer and manage domain names and DNS from your AI agent.
Buy & manage domains from any AI chat: availability, register, DNS, email forwarding, AI bot stats.
Domain search, registration, DNS, marketplace, and checkout with your AI agent.
Find, register, and manage domains from any AI chat or agent
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables natural language domain management through Dynadot, supporting domain registration, DNS configuration, transfers, WHOIS contacts, and bulk operations across 106 API actions.1028 npm13MIT

Name.com MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to perform comprehensive domain management tasks through the Name.com API, including registration, DNS management, and transfers. It dynamically generates tools from the OpenAPI specification to facilitate natural language interaction with all Name.com services.210 npm3MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Gandi domains and LiveDNS records directly via the Gandi API v5. It supports comprehensive domain management operations and full CRUD functionality for various DNS record types.3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to check domain availability, purchase domains via Stripe, and perform full DNS and nameserver management. It facilitates automated domain lifecycle tasks like record updates and transfer locks without requiring CAPTCHAs.MIT