PaidSync>Blog>Connect Google Ads to Cline with MCP

Connect Google Ads to Cline with MCP

Founder written
Author: Ahmed Ashraf|4 min read|Updated October 24, 2026
$1B+ ad revenue generated $500M+ managed Ex-Scandiweb paid media lead 630+ MCP tools

To connect Google Ads to Cline, add a remote server of type streamableHttp with the URL https://mcp.paidsync.ai/mcp, either in the Remote Servers tab or in cline_mcp_settings.json. Cline can then call PaidSync.ai tools for Google Ads, Meta Ads and 12 other platforms.

What Cline Needs

Cline treats PaidSync.ai as a remote MCP server. Its docs recommend the Streamable HTTP transport, and you need:

Cline's docs say that leaving type out falls back to the legacy sse transport, so set it explicitly.

How the Connection Works

SettingValue
TypestreamableHttp
URLhttps://mcp.paidsync.ai/mcp
Settings file (CLI)~/.cline/data/settings/cline_mcp_settings.json
IDE routeMCP Servers icon, Remote Servers tab
AuthoriseAuthorize OAuth in the CLI wizard, or a Bearer header

The docs only mention OAuth briefly, as an Authorize OAuth action in the CLI wizard. If you prefer a key, a PaidSync.ai API key in an Authorization header reads and previews on Google Ads.

How to Connect Google Ads to Cline in 5 Steps

Do these in order. The code box holds the exact setup from Cline MCP configuration docs.

1

Connect Google Ads to PaidSync.ai

Sign up at paidsync.ai and connect Google Ads on Google's own sign-in screen.

2

Open Remote Servers

In the Cline panel open the MCP Servers icon and go to the Remote Servers tab.

3

Fill in the form

Enter the name paidsync, the URL from the box below and Streamable HTTP as the transport, then click Add Server.

4

Authorise

From the CLI run cline mcp and use Authorize OAuth, or add a Bearer header if you use a key.

5

Test one tool call

Ask Cline to list your Google Ads accounts and confirm a PaidSync.ai tool runs.

cline_mcp_settings.json

{ "mcpServers": { "paidsync": { "type": "streamableHttp", "url": "https://mcp.paidsync.ai/mcp", "disabled": false, "autoApprove": [] } } }

How to Check the Connection

Leave autoApprove empty at first, so Cline asks before it calls any tool.

"List my Google Ads accounts and set the one called Main as active."
Run this to confirm the connection.
"Run get_wasted_spend_report for the last 30 days and list the search terms with cost and no conversions."
Run this to confirm the connection.

How PaidSync.ai Protects You

Setup follows Cline's MCP documentation, checked on 24 October 2026. The page describes OAuth only briefly. Source: Cline MCP configuration docs. 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

Does Cline support remote MCP servers?

Yes. Cline's docs describe remote servers with a URL and a Streamable HTTP transport.

Which transport should I pick?

Streamable HTTP, which Cline recommends. PaidSync.ai's endpoint speaks it.

Do I need an API key in Cline?

Not necessarily. The CLI offers an Authorize OAuth action. A Bearer header with a key also works for reports and previews.

Does it work for Meta Ads?

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

How much does it 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