CueScout.

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

AI clients

CueScout in Zed

Zed keeps MCP servers in its own settings.json under `context_servers` rather than in a separate file. The server body is the same as everywhere else; the wrapper is Zed-shaped.

@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: Zed settings.json, under context_servers

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 Zed settings

    cmd-, on macOS, or the `zed: open settings` command. It is the same settings.json that holds your theme and keymap.

  3. 3.Add the server under context_servers

    Merge this into your existing settings object rather than replacing it.

    Zed settings.json

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

  4. 4.Check the assistant panel

    The server and its tools appear in the assistant's tool list once Zed picks up the settings change.

What this does not do

  • Public pages only, read over HTTP.
  • Zed's context server support moves faster than most clients; if the key shape here does not match your build, Zed's own docs are the authority.
  • Nothing is stored between calls.

Frequently asked questions

Why is the key different?

Zed named the concept "context servers" before the ecosystem settled on mcpServers. It speaks the same protocol — only the settings key differs.

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

VS Code

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

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