English Français العربية

Tag Pilot Search Console

Official registry Search and web

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @tagpilot/search-console-mcp
Claude Code 
claude mcp add tag-pilot-search-console -e 'TAGPILOT_API_KEY=<your tagpilot_api_key>' -e 'SEARCH_CONSOLE_MCP_NO_BROWSER=<SEARCH_CONSOLE_MCP_NO_BROWSER>' -e 'SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS=45' -- npx -y @tagpilot/search-console-mcp@0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "tag-pilot-search-console": {
            "command": "npx",
            "args": [
                "-y",
                "@tagpilot/search-console-mcp@0.1.0"
            ],
            "env": {
                "TAGPILOT_API_KEY": "<your tagpilot_api_key>",
                "SEARCH_CONSOLE_MCP_NO_BROWSER": "<SEARCH_CONSOLE_MCP_NO_BROWSER>",
                "SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS": "45"
            }
        }
    }
}

Environment variables

  • TAGPILOT_API_KEY secret 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 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 How long a tool call waits for the browser sign-in before returning the link.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Tag Pilot MCP servers
  2. Repository layout
  3. Development
  4. Releasing
  5. License

Tag Pilot MCP servers

Free, read-only Model Context Protocol servers from Tag Pilot. No Google Cloud setup and no API key to copy: add a server, ask a question, and approve once in your browser.

PackageWhat it readsInstall (Claude Code)
@tagpilot/ga4-mcpGoogle Analytics 4: reports, funnels, realtime, property setup, tracking-health checksclaude mcp add ga4 -- npx -y @tagpilot/ga4-mcp
@tagpilot/search-console-mcpGoogle Search Console: search performance, period comparisons, SEO opportunities, URL inspection, sitemapsclaude mcp add search-console -- npx -y @tagpilot/search-console-mcp

Each package README has the install options for Claude Desktop (.mcpb), Cursor, VS Code and Gemini CLI, how connecting works and what Tag Pilot sees, the tools and troubleshooting. gemini extensions install https://github.com/tagpilot/ga4-mcp installs the GA4 server (Gemini CLI only installs from a repo root).

Repository layout

packages/mcp-core            shared, not published: device connect, PKCE, token cache, broker
                             endpoints, CLI (serve/login/logout/status), Google HTTP client
packages/ga4-mcp             @tagpilot/ga4-mcp
packages/search-console-mcp  @tagpilot/search-console-mcp
scripts/                     build (esbuild), .mcpb build and smoke test

The published packages bundle the core into dist/index.js with esbuild; the MCP SDK and zod stay npm dependencies. The .mcpb extensions are one fully bundled file each.

Development

npm install
npm run check      # typecheck + lint + unit tests (all packages)
npm run build      # → packages/*/dist/index.js
npm run e2e        # built servers over stdio against a mock broker and mock Google
npm run mcpb       # → packages/*/tagpilot-<name>-<version>.mcpb
npm run mcpb:smoke # unpack each bundle, check its tools, run the e2e against it

Releasing

Per package, from its directory: bump the version in package.json, src/version.ts, server.json, mcpb/manifest.json and the Gemini extension (GA4: repo-root gemini-extension.json); npm test checks they match. Then:

  1. npm publish --access public from the package directory.
  2. Push a tag <package>-v<version> (ga4-mcp-v0.3.1, search-console-mcp-v0.1.0): the Publish to MCP Registry workflow publishes that package's server.json.
  3. Create a GitHub release for the tag (gh release create <tag> --generate-notes). The Release .mcpb extensions workflow builds, smoke-tests and attaches both tagpilot-ga4-mcp.mcpb and tagpilot-search-console-mcp.mcpb to every release, so the releases/latest/download/<asset> links in the READMEs, the app and the website always work, whichever package was released last. Two assets also keep gemini extensions install on the source archive: with a single asset, Gemini CLI would try to install that file as the extension.

License

Apache License 2.0. The license does not cover the Tag Pilot name or logo (see NOTICE).

Frequently asked questions

What is Tag Pilot Search Console?

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

How do I install Tag Pilot Search Console?

It runs on your machine. In Claude Code: claude mcp add tag-pilot-search-console -e 'TAGPILOT_API_KEY=<your tagpilot_api_key>' -e 'SEARCH_CONSOLE_MCP_NO_BROWSER=<SEARCH_CONSOLE_MCP_NO_BROWSER>' -e 'SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS=45' -- npx -y @tagpilot/search-console-mcp@0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Tag Pilot Search Console need an API key?

Yes. It expects TAGPILOT_API_KEY, which you set in its configuration.

Is Tag Pilot Search Console open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Tag Pilot Search Console?

It is published by tagpilot. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.