CueScout.

See which conversations AI answers actually read about your category, and get into them.

AI clients

CueScout in Claude Desktop

Claude Desktop is where the non-terminal version of this belongs. Once the server is registered you ask in plain language — "does Perplexity mention us when someone asks about X" — and get back the answer, the competitors it named instead, and the pages it built the answer from.

@cuescout/mcp is not on npm yet and the source is not public yet, so there is no way to run the server locally today. The config below is what you will paste when it lands. In the meantime the same five checks are available as public HTTP endpoints that need no account and no key — they are listed with each tool below, and an agent can call them directly.

Where the config lives: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows

Setting it up

  1. 1.Not installable yet

    @cuescout/mcp is not on npm yet and the source is not public yet, so there is no way to run the server locally today. The config below is what you will paste when it lands. In the meantime the same five checks are available as public HTTP endpoints that need no account and no key — they are listed with each tool below, and an agent can call them directly.

    What works today

    curl -s https://cuescout.com/api/public/ai-readiness \
  -H 'content-type: application/json' \
  -d '{"url":"https://yoursite.com"}'

  2. 2.Open the config file

    Settings → Developer → Edit Config opens it directly, which is easier than finding it. On macOS it is in Application Support; on Windows it is under %APPDATA%.

  3. 3.Add the server block

    If the file already has an mcpServers object, add this entry inside it rather than replacing the object — a second mcpServers key silently wins over the first and takes your other servers away.

    claude_desktop_config.json

    {
  "mcpServers": {
    "cuescout": {
      "command": "node",
      "args": ["/absolute/path/to/cuescout/services/mcp-public/dist/index.js"]
    }
  }
}

  4. 4.Restart Claude Desktop

    Fully quit it rather than closing the window — the config is read at launch. The tools appear under the connectors icon in the composer once it comes back.

What this does not do

  • The config is read at startup only, so every change needs a restart.
  • The tools read public pages, and cannot see anything behind a login.
  • Nothing is stored between calls. This answers "what is true right now", not "what changed since last month".

Frequently asked questions

The tools do not appear after editing the config.

Nearly always one of two things: the app was closed rather than quit, or the JSON does not parse. Claude Desktop fails silently on a malformed config, so paste it through a JSON validator before restarting.

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?

No. The public endpoints write nothing to a database. If you want the same checks tracked over time against a site you own, that is the paid product.

Related

AI clients

Claude Code

One `claude mcp add` line, then ask about your site's AI visibility mid-session.

AI clients

Cursor

One block in ~/.cursor/mcp.json, and the agent editing your site can check what engines see of it.

AI clients

ChatGPT

The MCP server will not fit — ChatGPT needs a remote one. The public API is the route that works.

Every integration we publish

Run 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.

Run the free checkTrack it over time