MCP setup
Connect your AI client
Choose your client below. You do not need to sign in on this website first; adding the server starts secure Google authorization in your browser.
One endpoint for every compatible client
Streamable HTTP MCP endpoint
https://searchconsole.ai/mcp
No API key or copied access token is required. SearchConsole.ai requests read-only Google Search Console access through OAuth.
Codex
Paste this into a Codex task:
Add a user-level remote Streamable HTTP MCP server named searchconsole-ai with URL https://searchconsole.ai/mcp. Authenticate it with OAuth in my browser, then use SearchConsole.ai to list all Google Search Console properties I can access.Terminal alternative
Add the server from the Codex CLI:
codex mcp add searchconsole-ai --url https://searchconsole.ai/mcpCodex should open your browser and start OAuth automatically. If it does not, or authentication is interrupted, run this fallback command:
codex mcp login searchconsole-ai- Approve the SearchConsole.ai connection in your browser.
- Restart Codex and open a new task.
Method 2: Install from the Codex app
- Open Settings > MCP servers and select Add server.
- Enter searchconsole-ai, choose Streamable HTTP, and use
https://searchconsole.ai/mcp. - Save the server, restart Codex, then select Authenticate.
Final step: Start your SEO audit
Start a new chat with the project for a property (website) available in your connected Google Search Console account, then paste this prompt:
Use SearchConsole.ai to audit my SEO and identify my highest-impact opportunities. Read and follow the SearchConsole.ai SEO analysis playbook before analyzing the data. Then implement every evidence-backed, safe, non-destructive improvement that can be completed in the currently open website repository now. Do not produce a day-by-day or 30-day implementation plan. Save the completed audit as a Markdown report using the repository's documentation convention or docs/seo/search-console-audit-YYYY-MM-DD.md. After the audit, suggest a follow-up re-audit cron job or client automation so I do not have to remember it, and offer to create docs/seo/search-console-re-audit.md as the job instructions. The re-audit file must reference the exact previous audit report and require the next run to compare against it. Separately suggest a weekly Search Console history cron job or client automation, offer to create docs/seo/search-console-weekly-history.md as its instructions, and save dated snapshots under docs/seo/search-console-history/ so I can review historical data. Ask before deployment, publishing, destructive changes, or external-system mutations. Ask before creating an external schedule or scheduled-task files.Claude Code
- Run these commands in your terminal:
claude mcp add --transport http searchconsole-ai --scope user https://searchconsole.ai/mcp
claude mcp login searchconsole-ai- Approve the SearchConsole.ai connection in the browser window.
Final step: Start your SEO audit
Start a new chat with the project for a property (website) available in your connected Google Search Console account, then paste this prompt:
Use SearchConsole.ai to audit my SEO and identify my highest-impact opportunities. Read and follow the SearchConsole.ai SEO analysis playbook before analyzing the data. Then implement every evidence-backed, safe, non-destructive improvement that can be completed in the currently open website repository now. Do not produce a day-by-day or 30-day implementation plan. Save the completed audit as a Markdown report using the repository's documentation convention or docs/seo/search-console-audit-YYYY-MM-DD.md. After the audit, suggest a follow-up re-audit cron job or client automation so I do not have to remember it, and offer to create docs/seo/search-console-re-audit.md as the job instructions. The re-audit file must reference the exact previous audit report and require the next run to compare against it. Separately suggest a weekly Search Console history cron job or client automation, offer to create docs/seo/search-console-weekly-history.md as its instructions, and save dated snapshots under docs/seo/search-console-history/ so I can review historical data. Ask before deployment, publishing, destructive changes, or external-system mutations. Ask before creating an external schedule or scheduled-task files.Cursor
Add to Cursor
- Close Cursor completely.
- Select Add to Cursor below.
- When Cursor reopens, go to Settings > Tools & MCP and enable SearchConsole.ai.
- Select Authenticate, then approve the connection in your browser.
If Cursor reports that anysphere.cursor-deeplink was not found, update or reinstall Cursor and try again.
Method 2: Manual configuration
Save this configuration in ~/.cursor/mcp.json:
{
"mcpServers": {
"searchconsole-ai": {
"type": "http",
"url": "https://searchconsole.ai/mcp"
}
}
}Final step: Start your SEO audit
Start a new chat with the project for a property (website) available in your connected Google Search Console account, then paste this prompt:
Use SearchConsole.ai to audit my SEO and identify my highest-impact opportunities. Read and follow the SearchConsole.ai SEO analysis playbook before analyzing the data. Then implement every evidence-backed, safe, non-destructive improvement that can be completed in the currently open website repository now. Do not produce a day-by-day or 30-day implementation plan. Save the completed audit as a Markdown report using the repository's documentation convention or docs/seo/search-console-audit-YYYY-MM-DD.md. After the audit, suggest a follow-up re-audit cron job or client automation so I do not have to remember it, and offer to create docs/seo/search-console-re-audit.md as the job instructions. The re-audit file must reference the exact previous audit report and require the next run to compare against it. Separately suggest a weekly Search Console history cron job or client automation, offer to create docs/seo/search-console-weekly-history.md as its instructions, and save dated snapshots under docs/seo/search-console-history/ so I can review historical data. Ask before deployment, publishing, destructive changes, or external-system mutations. Ask before creating an external schedule or scheduled-task files.Other
If your client supports remote Streamable HTTP servers and OAuth, give it this prompt:
Add a user-level remote Streamable HTTP MCP server named searchconsole-ai with URL https://searchconsole.ai/mcp. Authenticate it with OAuth in my browser, then use SearchConsole.ai to list all Google Search Console properties I can access.Otherwise, add https://searchconsole.ai/mcp manually as a remote Streamable HTTP server named searchconsole-ai.
Final step: Start your SEO audit
Start a new chat with the project for a property (website) available in your connected Google Search Console account, then paste this prompt:
Use SearchConsole.ai to audit my SEO and identify my highest-impact opportunities. Read and follow the SearchConsole.ai SEO analysis playbook before analyzing the data. Then implement every evidence-backed, safe, non-destructive improvement that can be completed in the currently open website repository now. Do not produce a day-by-day or 30-day implementation plan. Save the completed audit as a Markdown report using the repository's documentation convention or docs/seo/search-console-audit-YYYY-MM-DD.md. After the audit, suggest a follow-up re-audit cron job or client automation so I do not have to remember it, and offer to create docs/seo/search-console-re-audit.md as the job instructions. The re-audit file must reference the exact previous audit report and require the next run to compare against it. Separately suggest a weekly Search Console history cron job or client automation, offer to create docs/seo/search-console-weekly-history.md as its instructions, and save dated snapshots under docs/seo/search-console-history/ so I can review historical data. Ask before deployment, publishing, destructive changes, or external-system mutations. Ask before creating an external schedule or scheduled-task files.