Connect Search Console to Claude

Claude Desktop

Open Settings, then Connectors, then Add custom connector, and paste the AutoPSEO endpoint at https://app.autopseo.com/mcp. Claude fetches the tool list on connect, so a working connection lists the tools straight away.

• Streamable HTTP, so there is no local process to install
• Authorize in the browser, or paste a bearer key that looks like apk_live_ followed by 32 hex characters
• Ask for the property list first to confirm which account the connector resolved to

Claude Code

From a terminal, register the server once with claude mcp add, choosing the http transport and the same endpoint. Inside a session the /mcp command shows whether it attached and which tools it exposes.

• Project scope for one repository, user scope for all of them
• Keep the key in an environment variable rather than in a committed config file
• Useful next to the page you are editing, so the agent reads its performance before rewriting it

Ask for the analysis by name

Tool selection is much more reliable when the prompt names the report. "Run the cannibalization analysis for this property" beats "check for keyword overlap", because the first maps onto one tool and the second onto several.

• "Which pages lost the most clicks versus the previous 28 days?"
• "Show striking-distance queries between positions 4 and 10"
• "Compare last month with the same month last year"
• "Which queries dropped out of the top 100 this month?"

What the connection can reach

Only the properties your AutoPSEO account can already read. A read-only key cannot call a write tool at all, so no amount of prompting, from you or from a page Claude happens to read, can make it change anything.

When it does not connect

Claude calls the server from its own infrastructure, so a localhost or private address is refused. Use the hosted endpoint exactly as written, including the /mcp path, and check the key has not been revoked under Account, MCP API keys.