Let your agent read your search data

Connect a read-only SEORev workspace key to the REST API or MCP server.

Create a workspace key

  1. Sign in as a workspace owner.
  2. Open Settings → API keys and create a key for your agent.
  3. Copy it when it's shown; keys are displayed once. Revoke it in Settings when access is no longer needed.

A key reads only its workspace's sites. The API and MCP tools cannot change data or post a rank check or crawl.

Read through the REST API

Send Authorization: Bearer sr_live_… on every request. Replace the placeholder with your own key; keep it private.

The days parameter defaults to 28 and accepts 28, 90 or 365.

GET /api/v1/sites
Sites, keyword counts, and when rank checks and Search Console last ran.
GET /api/v1/portfolio?days=28
Search Console totals versus the previous window, top 3/10 counts, movers and things to fix.
GET /api/v1/sites/{slug}?days=28
Daily traffic, top queries/pages, keyword positions and history, and logged changes.
GET /api/v1/sites/{slug}/health
Things to fix, Google index status per page and the latest crawl.
GET /api/v1/sites/{slug}/weekly
This week's 'what moved' report for one site, plus ready-to-copy plain text.
GET /api/v1/weekly
This week's 'what moved' report for every site in the key's workspace.

Connect through MCP

SEORev serves Streamable HTTP MCP at /api/mcp. Add it to Claude Code with this command:

claude mcp add --transport http seorev https://seorev.app/api/mcp --header "Authorization: Bearer sr_live_…"

The command contains a placeholder, not a working key. Use your own workspace key locally.

The 5 read-only tools

  • list_sites
  • get_portfolio
  • get_site_report
  • get_site_health
  • get_weekly_report