Tag Pilot Search Console

Name: Tag Pilot Search Console
Author: tagpilot

by tagpilotversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.tagpilot/search-console-mcp

Install

Overview

Description from the maker (original English)

Free, read-only Google Search Console: performance, opportunities, URL inspection. No GCP setup.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: TAGPILOT_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: TAGPILOT_API_KEY, SEARCH_CONSOLE_MCP_NO_BROWSER, SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "search-console": {
      "command": "npx",
      "args": [
        "-y",
        "@tagpilot/search-console-mcp"
      ],
      "env": {
        "TAGPILOT_API_KEY": "your-value",
        "SEARCH_CONSOLE_MCP_NO_BROWSER": "your-value",
        "SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add search-console --env TAGPILOT_API_KEY=your-value --env SEARCH_CONSOLE_MCP_NO_BROWSER=your-value --env SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS=your-value -- npx -y @tagpilot/search-console-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "search-console": {
      "command": "npx",
      "args": [
        "-y",
        "@tagpilot/search-console-mcp"
      ],
      "env": {
        "TAGPILOT_API_KEY": "your-value",
        "SEARCH_CONSOLE_MCP_NO_BROWSER": "your-value",
        "SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "search-console": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tagpilot/search-console-mcp"
      ],
      "env": {
        "TAGPILOT_API_KEY": "your-value",
        "SEARCH_CONSOLE_MCP_NO_BROWSER": "your-value",
        "SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

TAGPILOT_API_KEY secret env
Optional. Leave unset: the first question connects this device to your free Tag Pilot account in the browser. Set a gsc:mcp key (tpk_…) only for CI or headless setups.
SEARCH_CONSOLE_MCP_NO_BROWSER env
Set to 1 to only return the Google sign-in link (open it in any browser) instead of opening a browser.
SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS env
How long a tool call waits for the browser sign-in before returning the link.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account tagpilot, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5654 servers in this category
Published to the registry more recently than 79% of the other 5654 servers in this category
Basic checks equal to or better than 100% of the other 5654 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Tag Pilot Search Console safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TAGPILOT_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Tag Pilot Search Console MCP

A free, read-only Model Context Protocol server for Google Search Console. Ask Claude, Cursor or any MCP client about your organic search: clicks, impressions, CTR and positions by query or page, what changed between two periods, SEO opportunities, Google's index status for a URL, and your sitemaps.

No Google Cloud setup, no API key to copy. You don't need a GCP project, OAuth client, service account or gcloud. Add the server, ask a question, and approve once in your browser.

claude mcp add search-console -- npx -y @tagpilot/search-console-mcp

Get started

Install in your AI client (below). No configuration needed.
Ask something, e.g. *"Which queries lost the most clicks this month?"* The first time, a browser window opens (or your AI shows a link and a code like ABCD-1234):

sign in to your free Tag Pilot account, or create one;
check that the code matches and approve this computer;
sign in with the Google account that can see your Search Console properties and allow read-only Search Console access.

Ask again. You're connected; the computer shows up under Connected devices on the Search Console MCP page.

Already use the Tag Pilot GA4 MCP? This is a separate server with its own connection (and its own Google consent), so you can install either or both.

Install

Client	How
Claude Desktop	Download the extension and open it (no Node.js needed)
Claude Code	`claude mcp add search-console -- npx -y @tagpilot/search-console-mcp`
Cursor	Add to Cursor, or the `mcp.json` below
VS Code	Install in VS Code
Windsurf, Zed, …	command `npx`, args `["-y", "@tagpilot/search-console-mcp"]` (stdio)
Gemini CLI	clone the repo, then `gemini extensions install ./ga4-mcp/packages/search-console-mcp`

Everything except the Claude Desktop extension runs the npm package with npx, so it needs Node.js 18 or newer. In the MCP Registry it's io.github.tagpilot/search-console-mcp.

Claude Desktop config file (claude_desktop_config.json), Cursor (~/.cursor/mcp.json) and similar clients:

"mcpServers": { "search-console": { "command": "npx", "args": ["-y", "@tagpilot/search-console-mcp"] } } }

Headless and CI: where nobody can approve in a browser, create a gsc:mcp key on the Search Console MCP page and set TAGPILOT_API_KEY=tpk_… in the server's environment. The device connect is then skipped and only the Google sign-in link is shown.

How connecting works, and what Tag Pilot sees

The same flow as the GA4 MCP (RFC 8628-style device connect, like gh auth login): it works from any browser on any device, also over SSH, in containers or WSL, because nothing listens on your machine.

Your Search Console data goes from your machine straight to Google (www.googleapis.com/webmasters/v3, searchconsole.googleapis.com). It never passes through Tag Pilot.
Tag Pilot only brokers the token exchange. It adds Tag Pilot's Google OAuth client credentials to Google's token endpoint and returns Google's answer. It stores no Google tokens and never logs them; it holds the one-time sign-in code for at most 10 minutes, and that code is useless without the PKCE verifier that stays on your machine.
Read-only. The only Google scope requested is webmasters.readonly. None of the tools can change anything in Search Console (no sitemap submits, no deletes).
Your credentials stay on your machine, in ~/.config/tagpilot/search-console-mcp/device.json (readable only by you).
Disconnecting: revoke the device on the Search Console MCP page, run npx -y @tagpilot/search-console-mcp logout, and remove the app's access at myaccount.google.com/permissions.

Tools

All tools are read-only. site_url is the property exactly as list_sites shows it: sc-domain:example.com for a domain property, or a URL prefix with its trailing slash (https://www.example.com/).

Tool	What it does
`list_sites`	Properties you can read (domain and URL-prefix) with your permission level. Start here.
`search_analytics`	Clicks, impressions, CTR and position by `date`, `hour`, `query`, `page`, `country`, `device`, `searchAppearance`; filters; search type (web, image, video, news, Discover, Google News); data state; aggregation; paging (up to 25,000 rows per call).
`compare_periods`	Period-over-period by query or page: both periods, deltas, new/lost rows, and property totals. Default: last 28 days vs the 28 days before.
`find_opportunities`	Tag Pilot analysis. `low_ctr`: page-one rows with many impressions but under half a typical CTR for their position. `striking_distance`: rows at average positions ~5–20 with enough impressions.
`inspect_url`	URL Inspection: Google's indexed version of one URL (verdict, coverage, last crawl, robots.txt, canonical chosen by Google vs declared, sitemaps, rich results).
`list_sitemaps` / `get_sitemap`	Submitted sitemaps: type, last submitted/downloaded, errors, warnings, submitted URL counts.
`connect`	Connects this computer: returns a link and a code for you to approve in the browser (your AI shows them; clients that support MCP URL elicitation offer to open the link). Say "connect my Search Console" to start it explicitly.
`connection_status`	Connected (with the device name), waiting for approval (link and code again), not connected, or what went wrong. Waits up to 25 s for an open sign-in to finish.

Things to know about Search Console data

Lag: data is typically available after 2–3 days. The default date range is the 28 days ending 3 days ago. data_state: "all" adds fresher, still-changing data; the result says from which date data is incomplete.
Dates are Pacific Time (Search Console's day boundary). Relative dates ("yesterday", "7daysAgo") are computed in Pacific Time too.
Anonymised queries: queries too rare to show (privacy) are left out of rows grouped or filtered by query, so per-query rows add up to less than the totals by date, country or device. compare_periods reports property totals separately for that reason.
Row limits: a call returns up to 25,000 rows (use start_row to page), and Google exposes at most 50,000 rows per day per search type, sorted by clicks.
Aggregation: grouping or filtering by page counts each URL separately (byPage), so totals differ from property-level totals.
Discover and Google News don't support aggregation_type: "byProperty".
Quotas (Google's): Search Analytics allows 1,200 queries per minute per site and per user, plus a load quota that long, query-and-page-level requests use up faster. URL Inspection allows 2,000 inspections per day and 600 per minute per property, so inspect_url is for a handful of important URLs, not whole sitemaps.

find_opportunities uses a rough benchmark CTR curve (position 1 ≈ 28%, 3 ≈ 10%, 10 ≈ 2%) to rank rows. It's a rule of thumb for prioritising, not Google data or a forecast.

Troubleshooting

"Not connected yet" (a link and a code like `ABCD-1234`): your AI shows them. Open the link in any browser (it doesn't have to be on this machine), sign in to Tag Pilot, check that the code matches, approve, and allow Search Console access, then tell your AI you're done: it retries your question (or calls connection_status). The server keeps checking in the background, so nothing needs restarting. The code is valid for 10 minutes; after that, ask again (or say "connect Search Console") for a new one. To connect from a terminal instead (e.g. over SSH), run npx -y @tagpilot/search-console-mcp login: it shows the link, the code in a box and a countdown, and waits until you approve.

"The signed-in Google account has no access to the Search Console property …": use list_sites and pass site_url exactly as listed (sc-domain: for domain properties, trailing slash for URL prefixes). To use another Google account, run npx -y @tagpilot/search-console-mcp logout and connect again.

"This computer was disconnected from Tag Pilot": the device was revoked; ask again to reconnect. "Your Google sign-in expired or was revoked": ask again and approve again.

Quota errors: wait a few minutes (Search Analytics) or until tomorrow (URL Inspection).

Check the setup: npx -y @tagpilot/search-console-mcp status. Logs go to stderr.

Configuration

Nothing is required. All variables are optional:

Variable
`TAGPILOT_API_KEY`	A `gsc:mcp` key for headless/CI setups. Skips the device connect.
`TAGPILOT_API_URL`	Tag Pilot API base URL. Default `https://api.tagpilot.io`.
`SEARCH_CONSOLE_MCP_NO_BROWSER`	`1` to only print/return the link instead of opening a browser.
`SEARCH_CONSOLE_MCP_BROWSER`	Browser to open (macOS app name, or a command on Linux/Windows).
`SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS`	How long a tool call waits for the connect before returning the link. Default 45.
`SEARCH_CONSOLE_MCP_CONFIG_DIR`	Credential directory. Default `~/.config/tagpilot/search-console-mcp`.

Development

See the repo README. SEARCH_CONSOLE_MCP_WEBMASTERS_API_URL and SEARCH_CONSOLE_MCP_INSPECTION_API_URL point the Google calls at a mock (used by npm run e2e).

Tag Pilot Search Console

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Tag Pilot Search Console MCP

Get started

Install

How connecting works, and what Tag Pilot sees

Tools

Things to know about Search Console data

Troubleshooting

Configuration

Development

License