Docs / Guides / SiteTR + Claude

SiteTR + Claude

Claude Code is the fastest way to drive SiteTR — one command registers all 18 tools, and the audit loop runs in the terminal you already work in.

What you need

The Claude Code CLI installed and logged in, and your SiteTR bearer token — where the token comes from covers how it’s issued. That’s it; no plugins, no local server process.

Add the server

shell

$ export SITETR_TOKEN="…the token from onboarding"

$ claude mcp add --transport http sitetr https://sitetr.com/api/mcp -H "Authorization: Bearer $SITETR_TOKEN"

$ claude mcp list

→ sitetr — 18 tools registered · ready

Claude Desktop instead?

Desktop uses a config file rather than a command. Edit claude_desktop_config.json (Claude Desktop → Settings → Developer) and restart the app:

claude_desktop_config.json

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

First question

Open Claude in any project and ask like you’d brief a consultant:

agent

you what’s wrong with my site and what do I fix first?

SiteTR // runs audit_site + decay_scan, joined with GSC

1. /pricing — LCP 4.8s, render-blocking hero image // critical

2. /blog/mcp-guide — clicks −41% vs last window // decay: critical

Every finding Claude relays carries evidence and a verify step — how that works.

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 — if Claude reports one, it’s the ceiling, not a bug.

← Docs home

SiteTR + Cursor →