Hosted MCP server

Connect Scout to your AI agent

Scout runs a hosted MCP (Model Context Protocol) server, so AI agents — Claude Code, Cursor, Codex, VS Code, Gemini CLI, anything that speaks MCP — can watch stores for you: list watches, add one from a URL you paste, pause a noisy shop, scan now, and read back what’s new. The endpoint authenticates with a Scout agent key, a long-lived Bearer credential made for agents (browser sessions expire in an hour; agents should not have to re-login).

https://scout.clarved.com/mcpStreamable HTTP (stateless JSON mode)

Checking your session…

What your agent can do

Tool	Does
`list_watches`	List the account's watches with cadence and last check
`add_watch`	Start watching a public collection URL
`update_watch`	Rename, re-cadence, pause, or resume a watch
`delete_watch`	Archive a watch (scans and emails stop)
`get_watch`	Latest scan plus the newest products seen
`trigger_scan`	Scan one watch now (no email; scheduled scans email)
`account_status`	Plan, watch limit, cadence options

The dogfood plan allows 10 watches per account, and agent keys use exactly the same limits and features as the web app — there is no privileged agent path.

Add Scout to your client

Claude Code

Run this in your terminal.

claude mcp add --transport http scout https://scout.clarved.com/mcp --header "Authorization: Bearer sk_scout_YOUR_KEY"

Cursor

Cursor → Settings → MCP → Add MCP server, or paste into ~/.cursor/mcp.json.

{
  "mcpServers": {
    "scout": {
      "url": "https://scout.clarved.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_scout_YOUR_KEY"
      }
    }
  }
}

Codex CLI

Add to ~/.codex/config.toml.

[mcp_servers.scout]
url = "https://scout.clarved.com/mcp"

[mcp_servers.scout.http_headers]
Authorization = "Bearer sk_scout_YOUR_KEY"

VS Code

Command Palette → MCP: Add Server, or paste into .vscode/mcp.json.

{
  "servers": {
    "scout": {
      "type": "http",
      "url": "https://scout.clarved.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_scout_YOUR_KEY"
      }
    }
  }
}

Gemini CLI

Add to ~/.gemini/settings.json.

{
  "mcpServers": {
    "scout": {
      "httpUrl": "https://scout.clarved.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_scout_YOUR_KEY"
      }
    }
  }
}

Any other harness (mcp-remote)

Bridges a remote HTTP MCP server for clients without native support.

npx mcp-remote https://scout.clarved.com/mcp --header "Authorization: Bearer sk_scout_YOUR_KEY"

Verify

Ask your agent to call account_status — it should answer with your email, the dogfood plan, and the 10-watch limit. Then try: “Watch https://shop.example/collections/new-arrivals daily and tell me what’s already on the page.” The first scan is a baseline, so nothing is emailed until the second scan finds something new.

Prefer plain REST?

The same agent key authenticates Scout’s JSON API: GET/POST https://scout.clarved.com/api/watches with Authorization: Bearer sk_scout_… covers the watch list, creation, updates, and per-watch scans. MCP is the same surface with tools an LLM can pick from.

Good to know

Scout only reads public collection and category pages — how Scout reads pages explains the rules. Keys are stored hashed, shown once, and can be revoked here or from your dashboard whenever an agent retires. If a key leaks, revoke it: agents holding the old key stop working immediately.