Loading
Tag Pilot Search Console
io.github.tagpilotClaim this server
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
npx -y @tagpilot/[email protected]Credentials from the publisher
- TAGPILOT_API_KEY — 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.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
TAGPILOT_API_KEY=<secret> SEARCH_CONSOLE_MCP_NO_BROWSER=<value> SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS=<value> claude mcp add io.github.tagpilot-search-console-mcp -- npx -y @tagpilot/search-console-mcp@0.1.0Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.tagpilot-search-console-mcp": { "command": "npx", "args": [ "-y", "@tagpilot/[email protected]" ], "env": { "TAGPILOT_API_KEY": "<secret>", "SEARCH_CONSOLE_MCP_NO_BROWSER": "<value>", "SEARCH_CONSOLE_MCP_AUTH_WAIT_SECONDS": "<value>" } } }}claude_desktop_config.json
Local · npmPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
- stdio
- Version
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ