To connect Google Ads to n8n, add the MCP Client Tool node to an AI Agent, set its endpoint to https://mcp.paidsync.ai/mcp and sign in with n8n's MCP OAuth2 credential. PaidSync.ai then gives your n8n workflow its Google Ads tools, and the same connection reaches Meta Ads, LinkedIn Ads and 11 other platforms.
n8n has a node for this: the MCP Client Tool, a sub-node you attach to an AI Agent node. It connects the agent to an outside MCP server and lets it call that server's tools. You need three things:
https://mcp.paidsync.ai/mcp.The node reads and writes only through the tools you let it use, so you stay in charge of what the workflow can touch.
| Setting | Value |
|---|---|
| Node | MCP Client Tool, attached to an AI Agent node |
| Endpoint | https://mcp.paidsync.ai/mcp |
| Authentication | MCP OAuth2 credential, with Use Dynamic Client Registration left on |
| Alternative for unattended runs | Bearer authentication with a PaidSync.ai API key |
| Tools to Include | All, Selected or All Except |
Two details catch people out. An OAuth sign-in belongs to the person who approved it, so a scheduled workflow is better off with a Bearer credential. And an API key can read and preview on Google Ads, but applying a Google Ads change needs the OAuth sign-in.
Do these in order. The code box holds the exact setup from n8n MCP Client Tool node docs.
Sign up at paidsync.ai, then connect Google Ads on Google's own sign-in screen. There is no developer token and no Google Cloud project.
In your workflow, open the AI Agent node, click the plus under Tool and choose MCP Client Tool. Enter the endpoint from the box below and choose HTTP Streamable as the transport if your n8n version lists it.
Under Authentication choose MCP OAuth2 and create a new credential. Leave Use Dynamic Client Registration on, click Connect and sign in with your PaidSync.ai login.
Set Tools to Include to Selected and pick the reports you want. Start with read-only tools such as get_wasted_spend_report.
Open the chat, or trigger the workflow, and ask the agent a question about your account. Check that the agent calls a PaidSync.ai tool.
n8n MCP Client Tool node settings
Endpoint: https://mcp.paidsync.ai/mcp
Server Transport: HTTP Streamable
Authentication: MCP OAuth2
Use Dynamic Client Registration: on
Tools to Include: SelectedAsk the agent to list your accounts first. If the answer names your Google Ads account, the node is connected.
Setup follows n8n's own documentation, checked on 24 October 2026. n8n's node page names an SSE endpoint field, so pick HTTP Streamable only if your version shows that option. Source: n8n MCP Client Tool node docs. Also n8n MCP credential docs. Every Google Ads tool is on the Google Ads MCP server page, and the full list of clients is on Connect your ads.
Yes. n8n's MCP Client Tool node can call a remote MCP server, and PaidSync.ai is one. Point the node at https://mcp.paidsync.ai/mcp and sign in.
No. PaidSync.ai holds the Google Ads connection, so n8n never sees a developer token or a Google Cloud project.
Yes. The same endpoint exposes Meta Ads tools. See the Meta Ads MCP server page for the full list.
n8n lists Bearer, header and OAuth2 options. A Bearer credential with a PaidSync.ai API key suits unattended runs, and it reads and previews on Google Ads.
PaidSync.ai is free for 15 tasks a month with no card. Pro starts at $99 a month. See pricing.
PaidSync.ai runs 630+ tools across 14 ad and analytics platforms. Connect your accounts once and use them in the AI assistant you already work in.
Get Started Free Book a Demo