AI clients
CueScout in Claude Code
Claude Code already has your repo open, which is where the answers to most readiness findings live. Adding the CueScout server means the check and the fix happen in the same session: you ask whether the crawlers can reach the site, and the model that reads the answer is the one holding your robots.ts.
- Where the config lives
- .mcp.json in the project root, or the `claude mcp add` command
What it does
Runs @cuescout/mcp through npx, so there is nothing to install first.
Setting it up
3 steps, and the last one proves it works.
Add the server
Run this from the project directory. Claude Code writes it to .mcp.json, so it is committed with the repo and every collaborator gets it.
In your project directory
claude mcp add cuescout -- npx -y @cuescout/mcpCheck it registered
The server should appear with its five tools. If it does not, the usual cause is the path in the config — the client needs an absolute one.
In a Claude Code session
/mcpAsk it something worth asking
The most useful first question is not "is my site OK" but a specific buying question in your category, because the answer names whoever the engine recommends instead of you.
A prompt
Ask cuescout whether ChatGPT names us when someone asks "best tool for <your category>", then check whether our robots.txt lets its crawler in.
What this does not do
- The tools read public pages. They cannot see anything behind a login on the site you point them at.
- The visibility check queries a live engine, so the same question can come back differently an hour later. That is the engines being non-deterministic, not the tool being unreliable.
- Nothing is tracked between calls. Trend lines over time are the paid product, not the MCP server.
Questions
Does the config get committed?
If you use `claude mcp add` from a project directory it writes .mcp.json in that project, which is meant to be committed. Use the user scope instead if you would rather keep it to your machine.
Does this need a CueScout account?
No. The five tools call public endpoints with no authentication — the same ones behind the free tool pages. There is no key to paste and nothing to sign up for.
What does it cost?
Nothing to you. Four of the five tools are HTTP fetches against the site you name. The visibility check puts a real question to a search-grounded engine, which costs us a model call, so it is rate-limited per IP.
Is any of this stored?
Each run keeps a short record: what you entered, a summary of the result, the time and your IP address, so the daily limits can be enforced. The privacy policy has the details. Nothing is added to a CueScout account. If you want the same checks tracked over time against a site you own, that is the paid product.
Related
All integrationsRun the checks on your own site
The readiness check is free, needs no signup and takes about half a minute. It works out what your site is built on and gives you the fixes written for it.