MCP servers · Google Search Console · MCP server
Connect Codex CLI to Google Search Console
One line gives Codex CLI your Google Search Console account as tools: 8 endpoints, sites, search analytics, sitemaps, called with your own connection. No key in the prompt, a receipt for every call, revoke Codex CLI's access alone any time.
Three steps
- Create a free 0n3 account and connect Google Search Console. Paste a key or sign in; it lands in your vault, encrypted.
- Install 0n3 into Codex CLI. OpenAI's terminal agent reads 0n3 over Streamable HTTP with a token from your environment.
- Ask Codex CLI: whoami. Then: "List sites in Google Search Console".
Put the token in your environment
export ON3_TOKEN="<your 0n token>"
Add it to your shell profile so Codex finds it next time.
The line above carries a placeholder; 0n3.app/install mints a real key named for Codex CLI and fills it in.
What Codex CLI can then do in Google Search Console
Sites · Add and remove properties7
List sites
GET /sitesGet a site
GET /sites/{siteUrl}Add a site
PUT /sites/{siteUrl}Delete a site
DELETE /sites/{siteUrl}List sitemaps
GET /sites/{siteUrl}/sitemapsSubmit sitemap
PUT /sites/{siteUrl}/sitemaps/{feedpath}Delete a sitemap
DELETE /sites/{siteUrl}/sitemaps/{feedpath}Search analytics · Clicks, impressions, CTR and position by query, page, country or device1
Search analytics
POST /sites/{siteUrl}/searchAnalytics/querySitemaps · Submit and inspect sitemaps0
Submit and inspect sitemaps
Google Search Console in other AI clients
Claude Code + Google Search ConsoleMCP server + skillClaude (desktop & claude.ai) + Google Search ConsoleconnectorChatGPT + Google Search Consoleconnector · GPT actionGemini CLI + Google Search ConsoleMCP serverCursor + Google Search ConsoleMCP serverVS Code (Copilot) + Google Search ConsoleMCP serverWindsurf + Google Search ConsoleMCP server