Skip to content

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. Runs @cuescout/mcp through npx, so there is nothing to install first.

Where the config lives
Zed settings.json, under context_servers

By Telman Gadimov · Updated

Setting it up

3 steps, and the last one proves it works.

  1. Open Zed settings

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

  2. Add the server under context_servers

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

    Zed settings.json

    {
  "context_servers": {
    "cuescout": {
      "command": "npx",
      "args": ["-y", "@cuescout/mcp"]
    }
  }
}

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

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?

Each run keeps a short record: what you entered, a summary of the result, the time and your IP address, so the daily limits can be enforced. The privacy policy has the details. Nothing is added to a CueScout account. 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.WindsurfOne block in mcp_config.json and Cascade can check what the engines see of your site.VS CodeA .vscode/mcp.json block — note the key is `servers`, not `mcpServers`.
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