Automate SEO tasks with Google Search Console & AI via MCP Server
Ready for 3.0What this workflow does
This AI workflow has 6 nodes and runs when an MCP client calls one of its tools. Along the way it connects HTTP Request. It also calls 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, 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)
- Http Request Tool
n8n-nodes-base.httpRequestTool - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger
From the author
🚀 Google Search Console MCP Server --- 📋 Description This n8n workflow serves as a Model Context Protocol (MCP) server, connecting MCP-compatible AI tools (like Claude) directly to the Google Search Console APIs. With this workflow, users can automate…