To connect Google Ads to Make, add a connection in Make's MCP Client app, choose New MCP Server, enter https://mcp.paidsync.ai/mcp and sign in with OAuth. A scenario can then call PaidSync.ai tools by name or let an AI step pick them, across Google Ads, Meta Ads and 12 other platforms.
Make connects to remote MCP servers through its MCP Client app, which is in open beta. It has two modules you will use:
You also need a PaidSync.ai login with Google Ads connected. The free plan covers 15 tasks a month.
| Setting | Value |
|---|---|
| App | MCP Client (open beta) |
| MCP Server | + New MCP Server |
| URL | https://mcp.paidsync.ai/mcp |
| Authentication | OAuth, or an access token for unattended scenarios |
| Redirect URI if asked | https://www.make.com/oauth/cb/mcp |
Make's page notes the app is in open beta and that its functionality and pricing may change. PaidSync.ai's sign-in is standard MCP OAuth, so you normally do not register anything by hand.
Do these in order. The code box holds the exact setup from Make MCP Client app page.
Sign up at paidsync.ai and connect Google Ads on Google's own sign-in screen.
In a scenario, add a module from the MCP Client app and click Add next to Connection.
Choose + New MCP Server, enter the URL from the box below and sign in with your PaidSync.ai login.
Use the Call a tool module with the tool name get_account_summary to see the connection work before you add AI.
Use Execute an action with AI and describe the task, for example a weekly wasted spend check.
Make MCP Client connection
MCP Server: + New MCP Server
URL: https://mcp.paidsync.ai/mcp
Authentication: OAuth (sign in with PaidSync.ai)Run the Call a tool module once on its own. If it returns your account summary, the connection is good.
Setup follows Make's MCP Client app page, checked on 24 October 2026. The page does not state which transport the app uses. Source: Make MCP Client app page. Every Google Ads tool is on the Google Ads MCP server page, and the full list of clients is on Connect your ads.
Yes. Make's MCP Client app connects to remote MCP servers, and PaidSync.ai is one.
No. The MCP route uses PaidSync.ai's tools, including reports, audits and changes, from inside a scenario.
Yes. The same server exposes Meta Ads tools. See the Meta Ads MCP server page.
Not for sign-in. Make also accepts an access token if you prefer one for unattended runs.
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