Connect Google Ads to Zapier with MCP

$1B+ ad revenue generated $500M+ managed Ex-Scandiweb paid media lead 630+ MCP tools

To connect Google Ads to Zapier, add the MCP Client connection on Zapier's Apps page, enter https://mcp.paidsync.ai/mcp as the server URL, choose Streamable HTTP and switch OAuth to Yes. Zapier's MCP Client is in beta. Once connected, a Zap step or a Zapier Agent can run PaidSync.ai tools across Google Ads, Meta Ads and 12 other platforms.

What Zapier Needs

Zapier works as an MCP client through an app called MCP Client. It gives you three kinds of step for any server you connect:

Triggers called New Tool and New Tool Result.
A search called Run Read-Only Tool.
An action called Run Tool.

You also need a PaidSync.ai login with Google Ads connected. The free plan covers 15 tasks a month.

How the Connection Works

Setting	Value
App	MCP Client (beta), added from Apps, then Add connection
Server URL	https://mcp.paidsync.ai/mcp
Transport	Streamable HTTP
OAuth	Yes, then sign in with your PaidSync.ai login
Bearer token	Optional, left empty when OAuth is on

Zapier's help article says MCP Client only supports tool calls and that only Streamable HTTP and SSE transports work. With OAuth set to Yes, the Bearer Token field is ignored.

How to Connect Google Ads to Zapier in 5 Steps

Do these in order. The code box holds the exact setup from Zapier MCP Client help article.

Connect Google Ads to PaidSync.ai

Add the MCP Client connection

In Zapier open Apps, choose Add connection and select MCP Client.

Enter the server details

Fill in the fields from the box below, then sign in with your PaidSync.ai login when Zapier opens the OAuth window.

Pick a step

In a Zap, add the MCP Client app and choose Run Read-Only Tool for reports or Run Tool for changes. Name the tool, such as get_wasted_spend_report.

Test the step

Run the step in the Zap editor and check that it returns your account data.

Zapier MCP Client connection

Server URL: https://mcp.paidsync.ai/mcp
Transport: Streamable HTTP
OAuth: Yes
Bearer Token: (leave empty)

How to Check the Connection

Start with the search step, because it only reads. Use Run Tool only once you trust the Zap.

Tool: get_account_summary, run through Run Read-Only Tool

Run this to confirm the connection.

Tool: get_wasted_spend_report, run through Run Read-Only Tool

Run this to confirm the connection.

How PaidSync.ai Protects You

Reads first. Run Read-Only Tool cannot change your account.
Sign-in for changes. Applying a Google Ads change needs the OAuth sign-in.
Your trust decision. Zapier's help article tells you to connect only to servers you trust. PaidSync.ai tokens are encrypted at rest.
A change log. Applied changes are logged, on a best-effort basis, with a before-and-after result.

Setup follows Zapier's help article, checked on 24 October 2026. Source: Zapier MCP Client help article. Every Google Ads tool is on the Google Ads MCP server page, and the full list of clients is on Connect your ads.

Frequently Asked Questions

Can Zapier connect to Google Ads through MCP?

Yes. Zapier's MCP Client can connect to a remote MCP server such as PaidSync.ai, and its steps then run that server's Google Ads tools.

Is Zapier's MCP Client free to try?

Zapier describes it as a beta feature. Check Zapier's pricing for the plan you are on.

Does this work for Meta Ads in Zapier?

Yes. The same server exposes Meta Ads tools. See the Meta Ads MCP server page.

Do I need a bearer token?

No. Set OAuth to Yes and sign in. A token is only needed for servers that use token authentication.

How much does PaidSync.ai cost?

PaidSync.ai is free for 15 tasks a month with no card. Pro starts at $99 a month. See pricing.

Connect your ads to Claude, ChatGPT, Gemini and more→Google Ads MCP Server with Full Write Access→PaidSync.ai MCP Server for 14 Ad Platforms→Build Your Own Ads Agent→

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