CONNECT & SUPPORT

A steady hand
with your DNS.

Start with a read. Make a plan. Keep the original records within reach.

Hosted connection status

Hosted sign-in is not open yet. Namecheap’s registration response did not allow our callback address, and a real sign-in attempt was rejected. We are keeping the hosted connection closed pending provider approval. The following connection steps apply only after that gate is cleared.

In an AI client that supports remote MCP with OAuth, add this server address: https://dns-pilot.cuelayer.workers.dev/mcp
Review the permissions, then sign in on Namecheap’s own website.
Ask: “List my domains, then inspect the DNS for my chosen domain.”
For a change, give the exact registered domain and the values supplied by your hosting or email service.

Download the local plugin. For Codex, the downloadable local plugin combines the official Namecheap connection with the local planning companion. The initial hosted directory submission received ownership feedback on October 5. The revised package identifies Jackson Alan Jesionowski as the publisher. No approved or published directory listing is available yet.

What the beta can do today

The local package contains the direct Namecheap connection plus the tested planner. Account sign-in still needs validation in your client. The hosted implementation contains reads, previews, reconciliation, and DNS lookup, but is not available for account connections yet. All hosted write tests use fixtures, not customer domains.

If a change looks wrong

Stop and inspect the domain in your Namecheap dashboard. Ask the assistant to reconcile the plan rather than retry it. Do not create repeated replacements or restore an old snapshot over newer edits. Provider confirmation, public DNS propagation, HTTPS readiness, and email delivery are separate checks.

Report a problem

Open a support issue ↗

Include the tool name, approximate time, expected behavior, and a redacted error message. Never post passwords, authorization tokens, full private records, or government identification. GitHub issues are public. Account-specific requests require separate verification before action.

Source and documentation