Support, security, and removal.
Rookery's hosted connector gives an authorized AI assistant access to your technical SEO crawl evidence and review-gated workflows. This page explains exactly what it can do, how to disconnect it, and where to report a problem.
Connection help
Start with the step-by-step connection guide. The connector uses browser-based OAuth; do not paste your Rookery password or an access token into an assistant.
If sign-in loops or the tools stay unavailable, remove the connector, restart the client, add the canonical URL again, and complete the entire browser consent flow. Workspace administrators may need to allow custom connectors or developer mode.
After Rookery's typed, audience-bound token security upgrade, a connector authorized on the older server must sign in one more time. If an existing connection reports an authorization error after that rollout, remove and reconnect Rookery once.
What access means
Read access covers your sites, audits, page evidence, issues, links, reports, crawl status, and exports. Write access permits five actions: starting crawls, drafting fixes, creating tasks, proposing a deploy, and generating a report.
Actions can use crawl quota or AI budget. A deploy action creates only a temporary review proposal. The MCP has no tool that can approve or execute a live-site deploy; only the customer can approve it inside Rookery.
Data and privacy
The connector sees only data available to the signed-in Rookery account. Your assistant provider may process the information it retrieves under that provider's account settings and privacy terms. Requested AI drafts and reports may also be processed by Rookery's configured AI model providers.
Review the Privacy Policy and Terms of Service. Email hello@rookeryseo.com for an access, deletion, or privacy request.
Report a security issue
Email hello@rookeryseo.com with the affected client, approximate time, request or audit ID, and steps to reproduce. Do not send passwords, OAuth tokens, customer exports, or other secrets by email.
For suspected unauthorized access, remove the connector immediately and follow the server-side revocation guidance below.
Remove Rookery from an assistant
Removing a connector stops that local client from using its saved connection. Server-side revocation is a separate step because an access or refresh token may remain valid until it expires or is revoked.
Claude on the web or desktop
ChatGPT
Claude Code
claude mcp remove rookery --scope user
Codex
codex mcp remove rookery
Revoke server-side access
If access may be compromised, reset your Rookery password to invalidate all existing Rookery sessions, including MCP access and refresh tokens. This signs you out everywhere. If you use Google-only sign-in or need help, email hello@rookeryseo.com and ask for all account sessions to be revoked.
Reconnect from a clean state.
After removing or revoking access, add Rookery again only from the canonical URL. The commands below do not contain credentials.
codex mcp add rookery --url https://rookeryseo.com/api/mcp
claude mcp add --transport http --scope user rookery https://rookeryseo.com/api/mcp