Read-only quick start
Connect SitePilot with the read-only quick start
This procedure uses two SitePilot commands, one Cursor reload, and one bounded inspection. It does not change content or promise a completion time.
01
Before you start
- Use an HTTPS WordPress site with SitePilot MCP 0.4.16 or later installed and active. Get the plugin from the Download page.
- Use a WordPress account that may authorize an Application Password.
- Install Node.js 22 or later and Cursor.
- Open an empty folder in Cursor.
02
Path boundary
This quick start is only the Cursor local-adapter path. For Codex, Claude Code, Antigravity, or agent-assisted setup, use the full beginner guide and choose the matching client path first.
- Do not switch to remote OAuth during this attempt.
- Do not repair Node or npm, create a helper script, or write a second MCP entry as part of these steps.
- If a checkpoint fails, stop and record the exact command and output. Do not continue to the next command.
03
Command 1: authorize read-only
Approve the Application Password request in WordPress. Continue only when the terminal reports site:read.
npx -y sitepilot-mcp@0.1.6 login --url https://your-site.example --scopes site:read --profile first-user-test --label first-user-test04
Command 2: configure Cursor
Reload the Cursor window once, then call sitepilot-inspect-site exactly once.
npx -y sitepilot-mcp@0.1.6 init --client cursor --profile first-user-test05
Pass condition
- The inspection succeeds.
- The result reports the expected WordPress and SitePilot versions.
- Granted scopes contain only site:read.
- No password, Application Password, access token, or refresh token appears in the evidence.