MCP servers · Google Site Verification · MCP server
Connect Codex CLI to Google Site Verification
One line gives Codex CLI your Google Site Verification account as tools: 3 endpoints, verify ownership, more, 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 Site Verification. 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: "Verify in Google Site Verification".
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 Site Verification
Verify ownership · Issue a DNS/meta/file token and claim the domain1
Verify
POST /webResourceMore · Everything else this app exposes.2
Get a token
POST /tokenList owned
GET /webResourceGoogle Site Verification in other AI clients
Claude Code + Google Site VerificationMCP server + skillClaude (desktop & claude.ai) + Google Site VerificationconnectorChatGPT + Google Site Verificationconnector · GPT actionGemini CLI + Google Site VerificationMCP serverCursor + Google Site VerificationMCP serverVS Code (Copilot) + Google Site VerificationMCP serverWindsurf + Google Site VerificationMCP server
