CueScout.

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

AI clients

CueScout in Cursor

Cursor is the client where these tools pay off fastest, because the agent that reads the finding is the one that can act on it. "The structured data check says sameAs is empty" is a sentence Cursor can turn into a diff without you switching context.

@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: ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one

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.Pick the scope

    ~/.cursor/mcp.json makes the server available in every project. .cursor/mcp.json inside a project keeps it to that one and travels with the repo. For a tool you will use on one site, the project file is the tidier choice.

  3. 3.Add the server block

    Cursor uses the same mcpServers shape as the rest of the ecosystem, so this block is identical to the Claude Desktop one.

    ~/.cursor/mcp.json

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

  4. 4.Enable it in Settings → MCP

    New servers show up in that panel with a toggle. A green dot and five tools means it started; a red one is usually a path that is not absolute.

What this does not do

  • The tools read your deployed site, not your working tree. A fix you have not shipped will not change the answer.
  • Public pages only — nothing behind a login.
  • No history. The check tells you the state now.

Frequently asked questions

Why does the check still fail after the agent fixed the code?

Because the tool fetched your live site. Every one of these runs against a URL over HTTP, so nothing changes until the fix is deployed.

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

Windsurf

One block in mcp_config.json and Cascade can check what the engines see of your site.

AI clients

VS Code

A .vscode/mcp.json block — note the key is `servers`, not `mcpServers`.

AI clients

Claude Code

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

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