zone-mcp

An MCP server for Zone.ee / Zone.eu hosting, built on the ZoneID API v2. Use it from Claude or any other MCP client to manage domains, DNS records, mail forwarders and webhosting. A generic, spec-aware request tool covers the rest of the API: mailboxes, MySQL, cron, SSH, FTP, Redis, PM2 and cloud VPS.

• Built on the MCP TypeScript SDK v2 (@modelcontextprotocol/server). It serves the 2026-07-28 protocol revision and still works with clients on the 2025 revisions.

• Uses the stdio transport. It needs Node.js 20 or newer.

Tools

Related MCP server: infomaniak-mcp-agent

Setup

1. Create an API token at my.zone.eu → Settings → Security → API keys. It is shown only once.

2. Give the server your ZoneID username and token. Use either option below.

Option A: macOS Keychain (recommended on a Mac). The token never appears in a config file.

security add-generic-password -U -s zone-ee-api -a <your ZoneID username> -w
# paste the token at the prompt
claude mcp add -s user zone -- npx -y github:aanndryyyy/zone-mcp

Option B: environment variables.

claude mcp add -s user zone -e ZONE_USERNAME=<username> -e ZONE_API_TOKEN=<token> -- npx -y github:aanndryyyy/zone-mcp

Claude Desktop, Cursor, and other clients using mcpServers JSON

{
  "mcpServers": {
    "zone": {
      "command": "npx",
      "args": ["-y", "github:aanndryyyy/zone-mcp"],
      "env": { "ZONE_USERNAME": "<username>", "ZONE_API_TOKEN": "<token>" }
    }
  }
}

If you stored the credentials in the Keychain, leave out the env block.

From a local clone

git clone https://github.com/aanndryyyy/zone-mcp.git
cd zone-mcp && npm install   # builds dist/ automatically
claude mcp add -s user zone -- node "$PWD/dist/index.js"

Environment variables

SSH tools

read_logs and get_ssh_access run your system ssh with your own keys; nothing is uploaded and no key is stored. They work on webhostings (shared and Privaatserver), not cloud VPS.

• Host-key pinning. The server's host keys are fetched with ssh-keyscan and accepted only when their SHA256 fingerprint matches the one the ZoneID API reports for that webhosting. They go into a temporary known_hosts file, removed on exit; ~/.ssh/known_hosts is not touched.

• No shell injection. The remote side always runs a fixed script. Filter text reaches it base64-encoded and is matched literally (grep -F).

• Read-only. Neither tool changes anything. To register a key or whitelist an IP, get_ssh_access points to the zone_api_request calls, which ask you to confirm. It never suggests switching SSH access from public to whitelist on its own, because that would lock out keys that connect from changing IPs, such as CI deploy keys.

• Untrusted output. Log lines contain whatever visitors and bots sent (URLs, user agents). Treat them as data, not instructions.

Example prompts

• "Show the last 50 5xx errors on shop.example.com from the past three days."

• "Why can't I SSH into example.com?"

• "Which of my domains expire in the next 30 days?"

• "Show the MX and TXT records for example.com."

• "Add a TXT record _acme-challenge.example.com with value abc123."

• "Point www.example.com at 192.0.2.10."

• "Forward info@example.com to me@example.org."

• "Create a daily 03:00 cron job on example.com that runs php artisan schedule:run." (This one uses describe_endpoint, then zone_api_request.)

Notes

• Confirmation before writes. If your client supports form elicitation, the server asks you to confirm before it runs update_*, delete_*, or a POST, PUT or DELETE through zone_api_request. The prompt shows the old and new values, or the method, path and body. If you decline, nothing is sent and the tool returns status: "declined" (or "cancelled" if you dismissed the prompt). The confirmation is bound to the exact arguments with a signed requestState, so a client cannot answer it in advance or reuse it for other arguments. Clients without form elicitation skip this step and rely on their own tool-approval prompt. Create tools rely on the client's own tool approval.

• DNS names are FQDNs. Zone stores record names as www.example.com. The DNS tools accept @, a bare label (www), or the FQDN, and convert it. update_dns_record changes only the fields you pass.

• Not available through the API: DNS TTLs (Zone manages them) and DNSSEC activation. Use my.zone.eu for these.

• Rate limit. The API allows 60 requests/min per IP. list_dns_records without type uses 11 requests, one per record type. A 429 comes back as a tool error.

• Paid operations. Some endpoints reachable through zone_api_request cost money, for example /order/domain/renew, /order/cloud and billing resources.

• Structured output. Every tool declares an outputSchema and returns structuredContent, with the same JSON as text. The API always returns arrays, so list tools return objects such as { domains, pager }. resource_url and _links are removed to save tokens.

• Path safety. zone_api_request accepts only paths under https://api.zone.eu/v2 and does not follow redirects, so your credentials are never sent to another host.

• The OpenAPI spec in spec/openapi.json is Zone's public API reference, bundled so the server can work offline.

Development

npm install
npm run build
npx @modelcontextprotocol/inspector node dist/index.js   # interactive testing

# End-to-end smoke test against your live account. It's read-only: the only write is a DELETE of a record id that
# doesn't exist. It uses about 30 requests, so wait a minute between runs.
npm test                    # 2026-07-28 protocol
PROTOCOL=legacy npm test    # 2025-era protocol

License

MIT. Not affiliated with Zone Media OÜ.