Namecheap has a long-standing XML API but no official MCP server, so AI tools connect through community projects. Its API needs a qualifying account and every call must come from a whitelisted IPv4 address. That suits a fixed server, not an AI assistant on a laptop. Plonki's hosted MCP server works from any client with OAuth or an API key, and its REST API is JSON with an OpenAPI spec.
| Plonki | Namecheap | |
|---|---|---|
| Official MCP server | Yes, hosted | No. Community servers only |
| API access | Any account, from any IP | Qualifying account plus a whitelisted IPv4 address |
| API format | JSON REST, OpenAPI 3.1 | XML |
| Test environment | Test keys on your normal account | Separate sandbox with a separate account |
| .au names | .com.au, .net.au, .org.au and .au | .com.au, .net.au and .org.au. Not .au on its own |
| Currency | AUD | USD by default |
Plonki works from anywhere: AI assistants, serverless functions and laptops, with no IP allowlist to maintain. It sells .com.au, .net.au, .org.au and .au on its own, with the eligibility details handled in the API.
Not an official one as of November 2026. Several community projects wrap the Namecheap API.
AI assistants and serverless functions don't call from a fixed address. Plonki uses OAuth and API keys instead, so it works from anywhere.
Add the MCP server to Claude Code:
claude mcp add --transport http plonki https://plonki.com.au/mcp
Get a free test key Read the docs
Checked November 2026. Products change, so check Namecheap's own documentation before deciding.