Connect n8n to Google Search Console

How to connect Google Search Console to n8n

1. 1

   Sign in to GSC PAP and copy your token

   Go to gscpap.com, click "Sign in with Google" and approve the read-only access. Choose which properties to authorize, then copy the bearer token the connect page shows once. For a workflow that reports on one client, mint a token scoped to just that site at app.gscpap.com/account/tokens.

2. 2

   Create a Bearer Auth credential

   In n8n, create a new credential of the Bearer Auth type and paste the token into it. Use the credential rather than typing the token into the node: credentials are stored encrypted and are not exported with the workflow JSON, which matters the first time you share a workflow with somebody.

3. 3

   Add an AI Agent, then the MCP Client Tool

   Build the workflow as usual: a trigger, then an AI Agent node with a chat model attached. Then add the MCP Client Tool node and connect it to the agent's tool input. The MCP Client Tool is a sub-node, so it does not sit in the main flow; it hangs off the agent.

4. 4

   Point it at GSC PAP

   Set the transport to HTTP Streamable and the endpoint to the URL below. For authentication choose Bearer and select the credential from step 2. The node also offers Header, Multiple Headers and OAuth2; Bearer is the right one here, because our OAuth uses dynamic client registration rather than a client id and secret you could paste into a credential.

   textCopy

   https://mcp.gscpap.com/mcp

5. 5

   Choose which tools the agent gets

   Tools to Include defaults to All, which hands the agent all 36 tools. For a report workflow that is more than it needs and it costs tokens on every run, so switch to Selected and name the handful the prompt actually uses. All Except is there too, if it is easier to exclude a few.

   textCopy

   list_sites, search_analytics_query, compare_periods, find_quick_wins, find_content_decay

6. 6

   Write the prompt once, then schedule it

   Give the agent a specific instruction rather than a vague one, because a scheduled run has nobody to ask a follow-up question. Then swap the manual trigger for a Schedule Trigger and send the output wherever it belongs.

   textCopy

   Call list_sites to find the property for example.com. Then use compare_periods for the last 7 complete days against the prior 7, ending 3 days ago. Then find_quick_wins for the same window, top 5. Write a short report: the click and position change first, then the five queries worth a title rewrite, as a markdown table. No preamble.

n8n MCP Client Tool: common issues

• ·If the node shows only an SSE Endpoint field, it is the older SSE-only shape and it cannot reach GSC PAP, which has no SSE endpoint. Update n8n. HTTP Streamable landed in the MCP Client Tool node later than SSE and then became its default, with SSE marked deprecated.
• ·There have been reports of the transport dropdown being ignored at runtime, with the workaround of setting the transport as an expression, =httpStreamable. If the node insists on SSE despite the dropdown, try that before concluding the server is at fault.
• ·Keep the /mcp path on the URL. https://mcp.gscpap.com without it is not an MCP endpoint.
• ·A GET to our endpoint answers 405 by design, because the server does not offer a server-to-client stream over GET. That is the documented behaviour for a streamable server that does not support it, and a correct client carries on with POST.
• ·n8n also has a standalone MCP Client step node, separate from the MCP Client Tool sub-node. On instances where the Tool variant was stuck on SSE, the step node already had HTTP Streamable, so it is a workable fallback.
• ·GSC PAP is not in n8n's MCP server registry, so the one-click registry shortcut will not list it. Add it as above with a credential.
• ·Scheduled workflows fail silently if nobody watches them. Our rate limits are 60 calls a minute and 1,000 an hour per user, which a weekly report will never reach, but a workflow retrying in a loop can.

Frequently asked questions