Use it from Claude or Cursor

Point an AI assistant at your own SEO data and ask questions in plain English — against your crawls, your rankings and your history, not a generic web search.

What this gives you

Most SEO integrations wrap a single API. This one is backed by everything the tool already stores — crawl findings, rank history from both sources, AI citations, Search Console, and every change the agent made — joined together. “Why did this page drop last month” needs all of it at once.

22 tools in total: reading your data, reading Search Console, and acting (running the agent, applying a queued fix, replying to a review).

Connecting a local client

Claude Desktop, Claude Code and Cursor run the server themselves — nothing is exposed and no token is involved. Open Settings → AI connection and copy the configuration shown there; it is filled in with your real paths already.

Connecting a chat app

For connectors that need a URL, the tool can serve the same tools over HTTP. It stays off until you generate a token.

Generate a read-only token for this. It reaches 15 of the 22 tools and cannot run the agent or change your site — which is what you want for a token living in someone else's settings screen. Requests are capped per token.

What it will not do

An assistant cannot edit your site directly — there is no “set the title” tool. Changes go through the agent, so your autonomy setting still decides what happens, and every change keeps its undo.

Numbers come back with their source attached, and a movement calculated across two different sources is reported as not comparable rather than as a confident figure.