CueScout.

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

AI clients

CueScout in VS Code

VS Code reads MCP servers for Copilot's agent mode, and it is the one client in this list that names the config key differently: `servers`, not `mcpServers`. Pasting a block from anywhere else without changing that key is the single most common reason a server does not appear.

@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: .vscode/mcp.json in the workspace, or the user-level mcp.json

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.Create .vscode/mcp.json in the workspace

    A workspace file keeps the server with the project and can be committed. The user-level config is the alternative if you want it everywhere.

  3. 3.Add the server block, with the `servers` key

    This is the VS Code shape. The body is identical to every other client — only the outer key changes.

    .vscode/mcp.json

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

  4. 4.Start it from the editor

    VS Code shows a Start action above the server entry in the JSON file, and the tools then appear in agent mode's tool picker. Agent mode has to be on — the tools are not available in ordinary chat.

What this does not do

  • Tools are available in Copilot agent mode only, not in plain chat.
  • Public pages only, read over HTTP.
  • The answers describe your deployed site rather than your workspace.

Frequently asked questions

The server does not appear at all.

Check the outer key. VS Code expects `servers`; a block copied from a Claude or Cursor config will say `mcpServers` and be ignored without an error.

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

Cursor

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

AI clients

Windsurf

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

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