Connect PageReflect to Claude with MCP

You need a PageReflect account, membership in the organization you want Claude to access, and owner/admin permission to issue API keys.

MCP access is a Pro feature. The package runs locally with Node 22.19 or newer and talks to PageReflect over HTTPS.

Open Settings → API & Webhooks in your PageReflect workspace. Create a new API key with a descriptive name like "Claude Desktop" or "Claude Code".

The token is shown once. Store it in a password manager before closing the modal. PageReflect only stores an Argon2id hash plus a short display prefix, so the raw token cannot be recovered later.

For Claude Desktop, paste the generated JSON block into your Claude Desktop MCP config and restart Claude. For Claude Code, use the generated `claude mcp add` command.

The package name is `@pagereflect/mcp`. It is a local stdio MCP server; your API key is passed through the `PAGEREFLECT_API_KEY` environment variable.

After restart, ask Claude to call `get_account`. It should return the connected PageReflect organization, the API key name/prefix, and the user who issued the key.

If `get_account` returns 401, the key is missing, mistyped, or revoked. If another tool returns an upgrade error, the organization no longer has Pro access.

`get_account` verifies the connection. `start_audit` queues a URL audit. `get_run` polls progress. `get_report` returns JSON or a signed PDF URL. `list_sites`, `get_history`, and `get_schedule` expose organization history.

Tool calls are scoped to the organization attached to the key and are logged in the dashboard with argument hashes rather than raw arguments.

Restart the MCP client after editing config. Confirm the command is `npx -y @pagereflect/mcp`, the environment includes `PAGEREFLECT_API_KEY`, and any self-hosted or preview install sets `PAGEREFLECT_API_URL`.

Revoke a key immediately if it is pasted into the wrong place. Issue a new key, update Claude config, and call `get_account` again.