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.
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.
| Setting | Value |
|---|---|
| Type | streamableHttp |
| URL | https://mcp.paidsync.ai/mcp |
| Settings file (CLI) | ~/.cline/data/settings/cline_mcp_settings.json |
| IDE route | MCP Servers icon, Remote Servers tab |
| Authorise | Authorize 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.
Do these in order. The code box holds the exact setup from Cline MCP configuration docs.
Sign up at paidsync.ai and connect Google Ads on Google's own sign-in screen.
In the Cline panel open the MCP Servers icon and go to the Remote Servers tab.
Enter the name paidsync, the URL from the box below and Streamable HTTP as the transport, then click Add Server.
From the CLI run cline mcp and use Authorize OAuth, or add a Bearer header if you use a key.
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": []
}
}
}Leave autoApprove empty at first, so Cline asks before it calls any tool.
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.
Yes. Cline's docs describe remote servers with a URL and a Streamable HTTP transport.
Streamable HTTP, which Cline recommends. PaidSync.ai's endpoint speaks it.
Not necessarily. The CLI offers an Authorize OAuth action. A Bearer header with a key also works for reports and previews.
Yes. The same server exposes Meta Ads tools. See the Meta Ads MCP server page.
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