Skip to content

AI clients

CueScout in Windsurf

Windsurf keeps its MCP servers in a single config under ~/.codeium, and Cascade picks up the tools once it reloads them. The setup is the same shape as every other client; the file lives somewhere different. @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.

Where the config lives
~/.codeium/windsurf/mcp_config.json

By Telman Gadimov · Updated

What it does

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.

Setting it up

4 steps, and the last one proves it works.

  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. The tool surface and the endpoints behind it are documented either way, so the direct HTTP call works today.

    What works today

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

  2. Open the MCP config

    Cascade's settings panel has a link to it, or edit ~/.codeium/windsurf/mcp_config.json directly. It uses the standard mcpServers shape.

  3. Add the server block

    Add the entry inside any existing mcpServers object rather than adding a second one.

    ~/.codeium/windsurf/mcp_config.json

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

  4. Refresh the server list

    Cascade has a refresh control in the MCP panel, which is faster than restarting. The five tools appear under the server once it connects.

What this does not do

  • Public pages only, read over HTTP.
  • The answers reflect your deployed site, not your editor buffer.
  • Nothing is stored between calls.

Questions

Does Windsurf need a restart?

Usually not — the MCP panel has a refresh that re-reads the config. A restart is the fallback when a server refuses to appear.

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

CursorOne block in ~/.cursor/mcp.json, and the agent editing your site can check what engines see of it.VS CodeA .vscode/mcp.json block — note the key is `servers`, not `mcpServers`.ZedZed calls them context servers — same block, different key, in settings.json.
All integrations

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 check Track it over time