Domeneshop MCP

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.

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.

1. Download domeneshop-mcp-<version>.mcpb from the latest release.
2. Open it (double-click, or drag it into Claude Desktop).
3. 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:

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:

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: npx
• args: ["-y", "domeneshop-mcp"]
• env: DOMENESHOP_API_TOKEN and DOMENESHOP_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 npm

In 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>"
      }
    }
  }
}

Access mirrors the MCP annotations each tool declares, which clients use to decide what to run without asking.

All eleven record types Domeneshop accepts are supported:

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.