Account, Security & Privacy
Where your data goes
- Search Console data goes from your computer straight to Google. The Search Console MCP runs on your computer and calls Google's Search Console APIs directly. Results never pass through Tag Pilot; they go only to the AI client you run.
- Tag Pilot only brokers the token exchange. When you sign in, Google sends the one-time authorization code to Tag Pilot's API. The API holds it for at most 10 minutes, until your copy of the Search Console MCP collects it, and then deletes it. The code can't be used without a secret (the PKCE verifier) that never leaves your computer. The MCP then exchanges the code, and later refreshes its tokens, through the API, which adds Tag Pilot's Google OAuth client credentials and returns Google's response.
- Tag Pilot stores no Google tokens and no Search Console data, and doesn't log codes or tokens. It records only which connected device made a request, and when, to show Last used and to apply rate limits.
- Limited Use. Tag Pilot doesn't sell or share Google user data, use it for advertising, or use it to train AI models. See the privacy policy, section 5.
Google permission
The only permission requested is https://www.googleapis.com/auth/webmasters.readonly: read-only access to the Search Console properties your Google account can see. None of the tools can change anything in Search Console: they can't submit or delete sitemaps, request indexing or remove URLs.
Connected devices
Approving a computer on app.tagpilot.io/connect creates a Tag Pilot key for that computer and product only, delivered straight to it: you never see or copy it. It can only exchange Google tokens for the Search Console MCP. A GA4 MCP device can't sign in to Search Console, and the other way round.
Devices are listed under Connected devices on the Search Console MCP page, labelled with the AI client and computer name (for example Search Console MCP · Cursor on dev-box), with when they were created and last used. The same list shows your GA4 MCP devices, marked by product.
What is stored where
| What | Where |
|---|---|
| This computer's Tag Pilot key and Google tokens | On your computer: ~/.config/tagpilot/search-console-mcp/device.json |
Google tokens for a TAGPILOT_API_KEY (CI setups) |
On that machine: ~/.config/tagpilot/search-console-mcp/<id>.json |
| Device label, created and last used time | Your Tag Pilot account |
| One-time sign-in code | Tag Pilot's API, for at most 10 minutes during sign-in, then deleted |
The files are readable only by you (mode 600 on macOS and Linux). Change the folder with SEARCH_CONSOLE_MCP_CONFIG_DIR.
Revoking access
- Revoke the device under Connected devices on the Search Console MCP page. Token refreshes stop, so it stops working within the hour.
- Delete the local credentials:
npx -y @tagpilot/search-console-mcp logout. - Remove the access at Google on myaccount.google.com/permissions.
Several Google accounts or computers
- Switch Google accounts: run
npx -y @tagpilot/search-console-mcp logout, then ask again and choose the other account at Google. - Several computers: connect each one on its own. Each gets its own device entry, so you can revoke one without affecting the others.
- CI: create a key under Create a key manually on the Search Console MCP page and set it as
TAGPILOT_API_KEY. Keep it in your CI's secret storage, not in a committed config file.
Open source
The package is open source under Apache 2.0: source on GitHub, package on npm.