TL;DR: ChatGPT and Claude can’t see your DNS, so they guess when a redirect breaks. Connect Domain Forward’s MCP server and they run real checks, then set up the redirect for you on the free plan. It takes about 2 minutes.
Your domain redirect doesn’t work, so you ask ChatGPT. It gives you a sensible list: check the A record, wait for propagation, maybe it’s the SSL certificate. You try each one, paste the output back into the chat, and go another round.
The answers sound right because the assistant knows how DNS works in general. It has no idea what your domain actually returns right now. Every answer is an educated guess based on whatever you pasted in.
That changes once the assistant can run the checks itself.
Why AI Assistants Guess About Your Domain
When you ask about a broken redirect, this is what happens:
- The assistant reads your question and anything you pasted.
- It matches that against common causes it learned in training.
- It lists the likely causes, usually in order of how often they come up.
- You test each one by hand and report back.
The assistant never sees your live DNS records, your certificate or the redirect hops. If your problem is a stale A record left over from an old host, or a Cloudflare proxy that blocks the certificate, you find out on the third or fourth round.
What MCP Changes
MCP (Model Context Protocol) is an open standard that lets AI assistants call tools. Domain Forward has two MCP servers:
- Free tools server, no login. Domain check, DNS propagation, SSL check, redirect chain, DNS instructions for your provider, redirect rules for your own server and QR codes. The same checks as our free tools.
- Account server, sign in once. Everything in the free server, plus listing, creating, updating and removing your redirects, domain status and traffic numbers.
With either one connected, the assistant runs the check, reads the result and tells you what’s wrong with your domain specifically. A typical exchange looks like this:
You: Why does https://oldbrand.com show a certificate error?
Assistant: (runs the domain check) The apex domain still has an A record pointing at your old host, so the certificate comes from there and doesn’t match. Change the A record to
138.68.125.144and remove the old one. www is already set up correctly.
With the account server connected, you can follow up with “Now redirect it to https://newbrand.com with a 301 and keep the paths”, and the assistant creates the redirect after you approve it.
How to Connect Claude
- In Claude, open Settings and go to Connectors.
- Choose Add custom connector and paste the server URL:
- Free tools:
https://tools.domain-forward.com/mcp - Your account:
https://api.domain-forward.com/mcp
- Free tools:
- For the account server, sign in to Domain Forward when Claude asks.
Using Claude Code instead? One command adds it:
claude mcp add --transport http domain-forward https://api.domain-forward.com/mcpThe Claude setup guide has the details.
How to Connect ChatGPT
- In ChatGPT, open Settings and go to Apps.
- Add an app and paste one of the server URLs above.
- For the account server, sign in to Domain Forward when ChatGPT asks.
The ChatGPT setup guide has the details.
What to Ask
These work well as a first try:
- “Why does https://example.com show a certificate error?”
- “Has the DNS for example.com updated everywhere yet?”
- “Is shop.example.com set up correctly for Domain Forward?”
- “Show all my redirects and which domains aren’t active yet.”
- “How much traffic did my redirects get last week?”
- “Redirect oldbrand.com to https://newbrand.com with a 301 and keep the paths.”
If DNS is still updating, ask again in an hour. DNS propagation usually takes 1 to 4 hours, and the assistant tells you which resolvers have the new records.
Keeping Changes Under Your Control
Both Claude and ChatGPT ask you to approve a tool before it runs, unless you turn that off. Read the request before you approve it: it shows the domain and the destination.
Every change also appears in your Domain Forward dashboard, the same as a change made by hand or through the REST API. If you only want the assistant to look, connect the free tools server. It can’t change anything.
Chat vs Dashboard vs API
| Task | AI assistant | Dashboard | REST API |
|---|---|---|---|
| Find out why a redirect fails | Yes, explains the fix | Shows DNS status | Yes, raw data |
| Create or change a redirect | Yes, after approval | Yes | Yes |
| Change hundreds of redirects | Slow | Slow | Best choice |
| Needs an account | Only to make changes | Yes | Yes |
Stop Pasting DNS Output Into the Chat
Every round of “try this, paste the result” costs you time while visitors hit a broken or insecure redirect. Connect the server once and the assistant looks at the real records.
You can create a free account and connect it in about 2 minutes. Your email keeps working. Domain Forward only uses A and CNAME records, and your MX records stay where they are. To check a single URL by hand instead, use the URL redirect tester.