New: drive dremaxx over MCP

From now on you can operate dremaxx not only from the console but also from an AI agent – over the Model Context Protocol (MCP). Claude Code, Claude Desktop, VS Code, Cursor, Windsurf, Zed and anything else that speaks MCP.

Personal access tokens

• You create tokens in the console under Profile → Access tokens.
• Each token carries its own scope: read only, write, or destructive as well.
• Only a hash is stored. You see the plaintext exactly once, when it is created.

One endpoint per module

• DNS Hosting – 17 tools
• Monitoring – 25 tools
• DynDNS – 11 tools
• Account: subscriptions, invoices, sessions, reviews – 12 tools
• DNS tools – 10 tools, usable with no token at all

What a token may do. Every tool call is dispatched internally through the same route as an ordinary API call. Scopes, roles, subscription entitlements, ownership checks, quotas and the audit log all apply unchanged. An agent can therefore never do more than you could yourself over HTTP with the same token. Destructive tools additionally require an explicit confirmation.

Setup, example configurations for the common clients and the token management are at dremaxx.de/mcp.