How to Use the Google Search Console MCP in Windsurf

Q: How does Windsurf connect to my Google Search Console account?

You configure the server in your mcpconfig.json file with your Google API credentials. Cascade handles the authentication token, allowing the agent to call tools like listsites directly.

Q: Can Windsurf use Google Search Console to submit URLs for indexing automatically?

Yes, Cascade chains inspecturl with submitsitemap to detect unindexed pages and push updated sitemaps. It handles the entire sequence without requiring separate prompts for each step.

Q: Does the Google Search Console MCP Server support managing multiple properties in Windsurf?

Yes, you can list all verified properties using listsites within the Windsurf interface. Cascade then targets specific domains using getsite to run localized diagnostics.

Q: How does Windsurf handle Google Search Console rate limits?

Cascade monitors API limits when calling querysearchanalytics or inspecturl. If a rate limit is hit, the agent pauses execution to prevent token exhaustion.

Windsurf's Cascade autonomously chains Search Console diagnostics and sitemap management to fix your organic indexing loops.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Google Search Console MCP to Windsurf

Create your Vinkius account to connect Google Search Console to Windsurf and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Google Search Console with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automated Index Diagnostics with Windsurf

Cascade uses `inspect_url` to check the actual index status of your pages without making you click through the web UI. If a page is missing, the agent doesn't stop there; it looks up your active sitemaps using `list_sitemaps` to see if the URL is even registered. You get a clear picture of why a page is not showing up on Google. By running these checks in sequence, Cascade isolates crawling bugs and tells you exactly what to fix in your code.

Programmatic Sitemap Management via MCP Server

This MCP Server exposes `submit_sitemap` and `delete_sitemap` so your AI agent can manage your crawling footprint directly. When you deploy new dynamic landing pages, Cascade detects the changes and registers the updated sitemap XML immediately. You avoid the lag of waiting for Google's natural crawl cycle. If a sitemap contains dead links, the agent pulls details with `get_sitemap` to verify the error count before purging the bad file.

Automated Traffic Analytics Extraction

The `query_search_analytics` tool feeds raw performance metrics directly into Cascade's context window. Instead of manually exporting CSVs, you tell the agent to find your declining queries, and it pulls the click, impression, and position data. Cascade parses the raw numbers to identify which directories lost traffic this week. It then correlates these losses with indexing errors to pinpoint technical issues.

Setup guide

Set up Google Search Console MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the Google Search Console MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Google Search Console payment history." If connected, Cascade will call the Google Search Console tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "google-search-console-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Search Console. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Google Search Console now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Google Search Console MCP in Windsurf

You configure the server in your mcp_config.json file with your Google API credentials. Cascade handles the authentication token, allowing the agent to call tools like list_sites directly.

Yes, Cascade chains inspect_url with submit_sitemap to detect unindexed pages and push updated sitemaps. It handles the entire sequence without requiring separate prompts for each step.

Yes, you can list all verified properties using list_sites within the Windsurf interface. Cascade then targets specific domains using get_site to run localized diagnostics.

Cascade monitors API limits when calling query_search_analytics or inspect_url. If a rate limit is hit, the agent pauses execution to prevent token exhaustion.

This MCP integration reads search traffic metrics, sitemaps, and URL index states. Vinkius runs the server in an isolated V8 sandbox, meaning your Google API credentials and search data never persist on disk.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript