Getting Started with Search Console MCP

Setup takes about two minutes and there's no key to copy: install the server, ask a Search Console question, and approve once in your browser.

1. Install it in your AI client

Everything except the Claude Desktop extension runs the npm package with npx, so it needs Node.js 18 or newer (node --version). The install buttons are on the Search Console MCP page in Tag Pilot; new to Tag Pilot? Create a free account, or skip this and let the first question take you there.

The server is also listed in the official MCP Registry as io.github.tagpilot/search-console-mcp.

Claude Desktop

1. Download tagpilot-search-console-mcp.mcpb (also on the Search Console MCP page).
2. Double-click it, or drag it into Settings → Extensions.
3. Click Install and make sure the extension is enabled. Leave the optional API key field empty.

Prefer the config file? Open Settings → Developer → Edit Config, add this to claude_desktop_config.json and restart Claude:

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

Claude Code

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

Add --scope user after claude mcp add to use it in every project. Then start a new Claude Code session, or reconnect with /mcp.

Cursor

Click Add to Cursor on the Search Console MCP page, or add the same mcpServers JSON as for Claude Desktop to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).

VS Code

Click Install in VS Code on the Search Console MCP page, or add it to .vscode/mcp.json:

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

Gemini CLI

The Search Console extension lives in a subfolder of the repository, so install it from a clone:

git clone https://github.com/tagpilot/ga4-mcp
gemini extensions install ./ga4-mcp/packages/search-console-mcp

Other MCP clients

Any client that runs local (stdio) MCP servers works, for example Windsurf (now Devin Desktop) or Zed: the command is npx and the arguments are -y @tagpilot/search-console-mcp.

2. Connect on the first question

Start a new session in your AI client (MCP servers load when a session starts), then ask something, for example "Which Search Console properties do I have?", or just say "connect my Search Console". Your AI client shows a clickable link and a code like ABCD-1234; clients that support it also offer to open the link for you.

1. Open the link: it goes to app.tagpilot.io/connect. Use any browser, on any device.
2. Log in to your free Tag Pilot account, or create one.
3. Check that the code and computer match what your AI client shows, and click Approve and sign in with Google. Only approve a code you just started yourself.
4. Choose the Google account that can see your Search Console properties and allow read-only Search Console access.
5. The page says Connected. Close the tab and tell your AI client you're done: it checks the connection and answers your original question.

You don't need a terminal: your AI client uses the connect and connection_status tools for this (see Tools Reference). The code is valid for 10 minutes. Over SSH, in containers or in WSL, open the link on any device with a browser. Prefer a terminal? npx -y @tagpilot/search-console-mcp login shows the link and a boxed code with a countdown.

Already connected the GA4 MCP? The Search Console MCP connects separately, with its own code and Google consent.

"Google hasn't verified this app"

Google is still reviewing Tag Pilot's app, so you may see this warning before the consent screen. Click Advanced, then Continue (or Go to … (unsafe)). See Troubleshooting if Google says the app is blocked.

Once connected, the computer shows up under Connected devices on the Search Console MCP page, for example Search Console MCP · Cursor on work-laptop.

3. Check the setup

npx -y @tagpilot/search-console-mcp status

It shows whether this computer is connected (with the first characters of its Tag Pilot key) and signed in to Google.

Headless and CI: an API key instead

Where nobody can approve in a browser, create a key on the Search Console MCP page under Create a key manually (it's shown only once) and set it as TAGPILOT_API_KEY in the server's environment:

claude mcp add search-console --env TAGPILOT_API_KEY=tpk_your_key -- npx -y @tagpilot/search-console-mcp

The Tag Pilot connect step is then skipped and only the Google sign-in link is shown, once. GA4 MCP keys don't work here, and Search Console keys don't work for the GA4 MCP.

Commands

With TAGPILOT_API_KEY set, status, login and logout work on that key's sign-in only.

Settings

Nothing is required. All settings are optional environment variables:

Next steps

• Browse the tools and example prompts.
• Something not working? See Troubleshooting.