Filters work great. Until you want something complicated. Try clicking through "find me ten French ecommerce domains, ten years or older, with a GBP listing, under fifty bucks." That's a sentence, not a dropdown sequence. So we built an MCP server. Claude can now talk to CatchDoms directly. You ask in plain English, it searches.
What MCP is
Model Context Protocol is how AI assistants like Claude call tools defined by a remote server. We expose four tools on our endpoint: search domains, get domain, list filters, get stats. You add our endpoint to your Claude Desktop config once, and from then on Claude can search the CatchDoms catalog from inside the chat. No tab switching, no copy-paste.
What you'll learn
- How to plug the CatchDoms MCP server into Claude Desktop. Five seconds of JSON config.
- Three prompts I run all the time, with real results:
- "Find me 10 French expired domains with Trust Flow above 15 and a GBP listing."
- "Find ecommerce domains in the fashion niche, age over 10 years, under fifty bucks."
- "Compare these three domains and tell me which is best for an affiliate site."
- How much time it saves compared to manual filtering. I've timed it.
- The API path for people who'd rather script. Apify actor, public REST endpoint.
- Why MCP is Pro only. Short answer, the cost on our side and the fit with the audience.
Transcript
The full transcript will be posted here once the video is recorded.