Docs / Guides / SiteTR + Cursor

SiteTR + Cursor

Cursor talks to SiteTR over HTTP MCP — one JSON block in mcp.json and the agent panel can audit, score, and monitor every site you track.

What you need

A current Cursor build (remote MCP servers are supported in the agent panel) and your SiteTR bearer token — where the token comes from covers how it’s issued.

Add the server

Project-wide: create .cursor/mcp.json in the repo. Global: ~/.cursor/mcp.json. Same block either way:

.cursor/mcp.json

{ "mcpServers": { "sitetr": { "url": "https://sitetr.com/api/mcp", "headers": { "Authorization": "Bearer YOUR-TOKEN" } } } }

Reload the window, then check Settings → MCP: sitetr should list 18 tools. If it shows a 401, the token is wrong; a 503 means the instance has no token configured yet.

First question

agent panel

you check example.com for decay — which pages are quietly losing clicks?

SiteTR // decay_scan — last two 28-day windows, refresh vs rewrite

1. /blog/mcp-guide — clicks −41% // critical · rewrite

2. /docs — clicks −12% // warning · refresh

Good to know

The token is read-only by default — submit_audit stays off until the operator enables writes. The expensive tools have per-tool rate limits; everything else reads stored results and stays cheap.

← SiteTR + Claude

Webhooks & alerts →