inwx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INWX_ENV | No | live (default) or ote for the INWX test system | live |
| INWX_PASSWORD | Yes | INWX password (required) | |
| INWX_USERNAME | Yes | INWX login (required) | |
| INWX_SHARED_SECRET | No | TOTP shared secret if two-factor auth is enabled on the account (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_infoA | Account details and prepaid balance of the INWX account (live). Read-only. |
| domain_listA | List domains in the account with status, nameservers, renewal mode and expiry. Read-only. Filter by substring or TLD. |
| domain_infoB | Full details of one domain in the account: status, contacts, nameservers, transfer lock, renewal mode, auth code where the registry exposes it. Read-only. |
| domain_checkA | Availability check for one or more domains (registered elsewhere, free, or transferable). Read-only. |
| domain_priceA | Price list for TLDs (registration, renewal, transfer) in the account currency. Read-only. |
| domain_transferA | WRITE, COSTS MONEY: start an inbound transfer of a domain to INWX. Needs the auth code from the current registrar, four contact handle ids (may be identical) and the nameservers to set. gTLDs add one year of runtime, .de/.eu keep theirs. |
| domain_updateA | WRITE: change nameservers, transfer lock, renewal mode or contacts of a domain already at INWX. Only the given fields change. |
| domain_renewA | WRITE, COSTS MONEY: renew a domain at INWX by N years. |
| domain_logA | Recent log entries for a domain (transfers, updates, registry messages). Read-only. |
| contact_listA | List contact handles (owner/admin/tech/billing) in the account. Read-only. |
| contact_infoB | Details of one contact handle. Read-only. |
| contact_createB | WRITE: create a contact handle (ORG or PERSON). For .de the owner needs a German address or a German admin contact. |
| nameserver_listB | List DNS zones hosted on INWX nameservers. Read-only. Not needed for domains whose DNS lives at Cloudflare. |
| nameserver_infoB | Records of one INWX-hosted DNS zone. Read-only. |
| api_callA | Expert tool: call any DomRobot method by name with raw params (see https://www.inwx.de/en/help/apidoc). WRITE methods execute for real in live mode; prefer the named tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct resource-and-action pair: account, domain, contact, nameserver, or raw API access. List vs. detail vs. write vs. read-only operations are clearly separated, so an agent should not easily confuse them.
Tool names follow a consistent resource_action snake_case pattern, e.g. domain_list, domain_info, domain_renew, contact_create, nameserver_list. The only generic name, api_call, is intentionally presented as an expert fallback, not as part of the normal naming pattern.
15 tools is at the upper bound of the ideal range, but each covers a necessary INWX domain-management concern: account, domains, contacts, nameservers, and raw API access. There is no obvious padding, and the scope is coherent.
The named tools cover reads plus domain transfer/update/renew and contact create, but miss high-level contact update/delete, domain registration, and nameserver zone modifications. The api_call escape hatch makes those operations possible, but only through raw low-level API calls.