--- title: "Google Search Console MCP Setup with ToolPiper on Mac" description: "Connect Google Search Console to your AI editor through ToolPiper's MCP server. Four tools: list sites, query analytics, inspect URLs, list sitemaps." date: 2026-05-12 author: "Ben Racicot" tags: ["Google Search Console", "GSC", "SEO", "OAuth", "MCP", "Privacy", "macOS"] type: "article" canonical: "https://modelpiper.com/blog/gsc-search-console-mcp-toolpiper/" --- # Google Search Console MCP Setup with ToolPiper on Mac > Connect Google Search Console to your AI editor through ToolPiper's MCP server. Four tools: list sites, query analytics, inspect URLs, list sitemaps. ## TL;DR ToolPiper exposes four Google Search Console tools over MCP. gsc_site_list lists your properties. gsc_analytics queries impressions, clicks, CTR, and position with date and filter support. gsc_inspect runs URL inspection. gsc_sitemap_list lists submitted sitemaps. Connect Google in ToolPiper's OAuth pane, register ToolPiper with your AI editor, ask SEO questions in natural language. Search Console is the highest-signal SEO data Google gives you, and the GSC UI is famously slow to answer the questions you actually have. Open it, pick a date range, drill into a query, drill into a page, lose track of the original question. The data's all there. The interface gets in the way. MCP lets your AI editor ask the same questions and get the answers in plain English. ## Why expose Search Console as MCP tools? Because the questions you ask about your site's organic traffic are conversational, not pivot-table-shaped. "Which pages dropped impressions last week" is faster to ask in chat than to construct as a manual report. ToolPiper's four GSC tools let your AI editor answer the question in one call instead of five clicks and a copy-paste. The four tools, each mapped to a concrete kind of question: - **`gsc_site_list`**. "Which properties do I have?" Enumerates the GSC properties your Google account has access to. Usually the first tool the editor calls in a session, to scope subsequent queries. - **`gsc_analytics`**. "What's happening with my traffic?" Queries the GSC Search Analytics API with date range, filters (query, page, country, device), and dimensions. Returns impressions, clicks, CTR, position. The editor formats the result based on your prompt. - **`gsc_inspect`**. "Is this URL indexed?" Wraps the URL Inspection API. Returns indexing status, last crawl date, mobile usability, page experience signals. Useful for checking whether a recent publish made it into Google's index. - **`gsc_sitemap_list`**. "What sitemaps have I submitted, and are they OK?" Lists submitted sitemaps with their submission date, last processed date, and error count. The fast check before you assume an indexing problem is on Google's side. ## How do I set up Google Search Console with ToolPiper? Connect Google in ToolPiper's OAuth pane. Register ToolPiper with your AI editor. Ask the editor a Search Console question in plain English. The editor calls the right tool with the right scope based on the prompt. Three steps from zero: 1. Connect Google. Open ToolPiper. OAuth pane. Click Connect on Google. Sign in with the account that owns your GSC properties. Grant the `webmasters.readonly` scope ToolPiper requests. The OAuth pane updates to show "Connected". This is the only setup specific to Search Console. The rest is generic MCP. 2. Register ToolPiper with your AI editor. Follow the matching guide for your editor: [Claude Code](/blog/claude-code-mcp-setup-toolpiper), [Cursor](/blog/cursor-mcp-setup-toolpiper), [Claude Desktop](/blog/claude-desktop-mcp-setup-mac), [Windsurf](/blog/windsurf-mcp-setup-toolpiper). Any MCP-capable editor works. 3. Ask a Search Console question. Start a chat. Try _"which pages on my site dropped impressions in the last 7 days?"_. The editor calls `gsc_site_list`, picks the property, calls `gsc_analytics` with the right date range and dimensions, and summarizes the result. ## What kinds of questions can I ask? Anything Search Console can answer about your site's organic traffic, plus comparison and inference questions an AI is better at than the GSC UI. The editor handles the API parameter shape. You ask in plain English. Example prompts that work end-to-end with the four tools: - _"Compare impressions and clicks between this week and last week. Which pages changed the most?"_ - _"Is the article at /blog/connect-toolpiper indexed yet? When was Google's last crawl?"_ - _"What queries did I rank in the top 3 for last month? Group by query intent."_ - _"List my top 10 declining pages by impressions, week over week."_ - _"Did my last sitemap submission process successfully? Any errors?"_ - _"Which of my pages have impressions but no clicks? Suggest a title or meta description fix for each."_ The last example is where AI editors pull ahead of the GSC UI. They can fetch the analytics, fetch the page content separately, and synthesize a recommendation. The GSC UI can't. ## How does ToolPiper handle Search Console API rate limits? Search Console has generous quotas for individual property owners (1,200 queries per minute per user). ToolPiper passes through your account's quota directly without batching or rate-limiting on its end. For most users this is invisible. For high-volume scripted queries, ToolPiper surfaces Google's quota errors when they happen. If you're running a lot of `gsc_analytics` queries in a tight loop, you may hit Google's per-minute limit. The error comes back as an MCP tool error with Google's message. Wait and retry, or break the query into fewer larger ones (longer date ranges, more dimensions per call). ## What if Search Console tools return permission errors? Three causes account for most permission errors. The connected Google account doesn't own the property. Workspace admin policies restrict third-party app access. The OAuth token expired and ToolPiper hasn't re-authenticated. Check the OAuth pane status first. 1. Property ownership. The Google account you connected has to own (or be granted access to) the GSC property you're querying. `gsc_site_list` only shows properties this account can see. 2. Workspace policy. On Google Workspace accounts, admins can restrict third-party app access. If ToolPiper isn't approved by your admin, the consent flow may succeed but tool calls fail with permission errors. Try a personal Google account first to isolate the issue. 3. Token expiry. If the OAuth pane shows "needs re-authentication", click Connect again. ToolPiper refreshes tokens automatically, but some policy changes invalidate refresh tokens and force a re-consent. For deeper OAuth troubleshooting, see [Connect ToolPiper to Your Cloud Accounts via OAuth on Mac](/blog/connect-toolpiper-oauth). ## FAQ ### Do I need a Search Console API key or a service account? No. ToolPiper uses OAuth on your personal Google account (or whichever account owns the GSC properties). The consent flow handles credentials. No API key, no service account JSON, no manual scope configuration. ### Can ToolPiper write to Search Console (submit sitemaps, request indexing)? Not currently. ToolPiper requests only the read-only Search Console scope (`webmasters.readonly`). Submitting sitemaps and requesting indexing would require write scopes, which we haven't shipped. Use the Search Console UI for those operations. ### How fresh is the data ToolPiper returns? As fresh as Google's API returns. Search Console analytics data typically lags by 2-3 days. URL Inspection returns near-real-time data for recently crawled URLs. The freshness floor is set by Google, not ToolPiper. ### Can my AI editor analyze multiple GSC properties at once? Yes. `gsc_analytics` takes a site URL parameter. The editor can call it multiple times in a session, once per property, and synthesize the results. For prompts like "compare traffic across all my sites", the editor typically does this automatically. ### Does the data ever leave my Mac on its way to Google? The tool call goes from ToolPiper directly to Google's Search Console API over HTTPS. ModelPiper's servers are not in that path. The data returns to ToolPiper, ToolPiper returns it to your AI editor, and the editor renders the answer for you. The OAuth token used to authenticate the request stays in your macOS Keychain.