Expose a full Google Search Console SEO toolkit over MCP
Ready for 3.0What this workflow does
This AI workflow has 19 nodes and runs when an MCP client calls one of its tools. Along the way it connects HTTP Request. It also calls googleapis.com, searchconsole.googleapis.com and indexing.googleapis.com over HTTP.
How it runs
Trigger: When an MCP client calls one of its tools.
No action steps found in the workflow JSON.
Services it uses
HTTP calls to: googleapis.com, searchconsole.googleapis.com, indexing.googleapis.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (2)
- MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Http Request Tool
n8n-nodes-base.httpRequestTool
From the author
Quick overview Turn n8n into a Google Search Console MCP server. This workflow exposes 18 tools any MCP client (Claude, Cursor, etc.) can call — search analytics, URL inspection, sitemaps, the Indexing API, site verification, ownership management, and…