Search Console MCP and cookieless analytics that Cursor, Claude Desktop, ChatGPT, Codex, Grok and other agents can query.
- Gemini CLI Search Console MCP — Connect Search Console history and cookieless analytics to Gemini CLI with gemini mcp add, an HTTP bearer token, and a GEMINI.md that keeps totals honest.
- Claude Code Search Console MCP setup — Add SiteLine's Search Console and analytics MCP servers to Claude Code with claude mcp add, a team-scoped bearer token, and a safe query order.
- ChatGPT Search Console MCP connector — Connect ChatGPT to a Search Console MCP with SiteLine’s OAuth connector. Query clicks and pages in chat. Never paste a bearer token into the transcript.
- Claude Desktop Search Console MCP — Claude Desktop can use SiteLine’s Search Console MCP as an OAuth connector or, in a local config, with a bearer token. Both are read-only.
- Claude connector for Search Console and analytics — Add SiteLine to Claude.ai as a custom connector: the OAuth approval, adding both servers, revoking access, and when to move to Claude Code.
- MCP for Search Console and analytics in Cursor — Point Cursor at SiteLine’s two HTTP MCP servers with a team-scoped bearer token. Query Search Console and analytics from the agent that edits your repo.
- SEO analytics for AI agents — Coding agents cannot log into Search Console or GA4. SiteLine exposes Search Console and cookieless analytics over MCP so agents can query real numbers.
- SiteLine MCP setup for AI coding agents — Connect Cursor, Claude Code, ChatGPT and other agents to SiteLine MCP: OAuth for connectors, a team bearer token for IDEs, two read-only servers.
- Why GA4 is a bad fit for AI agent workflows — GA4 has no agent interface. Explorations are not tool calls, BigQuery is a pipeline, and consent holes look like traffic crashes.