MCP servers · Google Site Verification · connector
Connect Claude (desktop & claude.ai) to Google Site Verification
One line gives Claude (desktop & claude.ai) 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 Claude (desktop & claude.ai)'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 Claude (desktop & claude.ai). Add 0n3 as a custom connector; sign in once through the 0n door.
- Ask Claude (desktop & claude.ai): whoami. Then: "Verify in Google Site Verification".
Claude desktop app and claude.ai
- Settings → Connectors → Add custom connector
- Name: 0n3 · URL: https://0n3.app/mcp
- Click Connect and sign in with your 0n account (email + password, or paste your 0n token)
- Turn the connector on in a chat and ask: "whoami"
This is the OAuth door: no token to paste, revoke it any time from 0n3 → Tokens.
The line above carries a placeholder; 0n3.app/install mints a real key named for Claude (desktop & claude.ai) and fills it in.
What Claude (desktop & claude.ai) 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 + skillChatGPT + Google Site Verificationconnector · GPT actionCodex CLI + Google Site VerificationMCP serverGemini CLI + Google Site VerificationMCP serverCursor + Google Site VerificationMCP serverVS Code (Copilot) + Google Site VerificationMCP serverWindsurf + Google Site VerificationMCP server