Home>Platforms>Google Ads MCP

Google Ads MCP Server for Claude and ChatGPT, PaidSync.ai

By Ahmed Ashraf|Updated November 18, 2026

PaidSync.ai is a hosted Google Ads MCP server that lets Claude or ChatGPT read your Google Ads account and make changes in it from a chat. It gives them 158 Google Ads tools (64 read, 94 write), manager (MCC) accounts included, no developer token, no Google Cloud project and nothing to host.

Setup starts with a PaidSync.ai account at paidsync.ai, where you connect Google Ads on Google's own sign-in screen. Then add PaidSync.ai from Claude's connector directory or ChatGPT's Plugin Directory and sign in. A good first question is "Show last week's spend and conversions by campaign." Creates run as a dry run first, new Search campaigns start paused, and changes that are hard to undo (pauses, removals and budget updates) are confirmed first.

The same connection covers Meta, TikTok, LinkedIn and 10 more platforms.

How PaidSync.ai keeps you in control

  • Preview first. Google Ads create tools run as a dry run by default. The first call shows what would be created and changes nothing.
  • New campaigns start paused. A new Search campaign is created paused, so nothing spends until someone enables it.
  • Approval before each change. In the PaidSync.ai workspace, every change waits as an approval card until a person approves it. From Claude or ChatGPT, your assistant's own approval setting decides whether it asks first.
  • A confirm for risky moves. Pauses, removals and budget updates refuse to run without an explicit confirm, and a budget change of more than 50 percent needs a second one.
  • A change log. Each live change is recorded with the user, the account, the tool and a before-and-after outcome. Read it in PaidSync.ai or ask the assistant.
  • Read-only when you want it. A PaidSync.ai API key can only read and preview on Google Ads. Tokens are encrypted at rest with AES-256-GCM, and disconnecting deletes them.

Every control, and what is not built yet, is listed on the secure Google Ads MCP server page.

Why PaidSync.ai instead of the free official connector

Since its 2 Nov 2026 release, Google's own Google Ads MCP server can create assets and manage labels: the release notes say "Implement asset and label management with propose-and-confirm flow" (v0.0.6 on GitHub, read 7 Nov 2026). PaidSync.ai reads and makes the changes you approve, on campaigns, budgets, bids and keywords too. Google publishes a free, open-source Google Ads MCP server that you host yourself. Its README on GitHub, checked on 7 November 2026, lists seven tools (a search tool for Google Ads queries, a lookup for resource metadata, a list of the accounts your login can reach, and four that create assets and manage labels, each proposed first and confirmed second) and setup steps to configure Python, enable APIs in your Google Cloud project, configure credentials and configure your MCP client. Google's own page says developer tokens "were sunset on September 9, 2026, and are no longer required in the latest version of the Google Ads MCP server" (developers.google.com, read 7 November 2026). It suits a developer who wants to host the code, read data and manage assets and labels.

PaidSync.ai is the hosted option for people who want Claude to act on the account. What you can check:

  • It makes changes, not only reports. Claude can change budgets, bids, status, keywords and negatives, and create Search, Performance Max, Display, Shopping and Demand Gen campaigns.
  • No developer setup. You add it from Claude's connector directory and sign in. There is no API key, no Google developer token, no Google Cloud project and nothing to host.
  • Many accounts in one connection. One connection holds several Google logins and works through manager (MCC) accounts, nested ones included.
  • More than Google. The same connection reaches 14 platforms and 630+ tools, including Meta, LinkedIn, Microsoft Ads and GA4, so one question can compare them.
  • Checks before changes. New campaigns and ads start paused or as drafts, budget edits run as a preview first, live pauses, enables and removals need an explicit confirmation, and a campaign budget move of more than 50% needs a second one.
  • Price. PaidSync.ai is free for 100 tasks a month, worth $50, with no credit card and no time limit. Pro is $99 a month for 1,000 tasks, or $75 a month billed yearly, and Team is $249 a month for 10,000 shared tasks and up to 20 seats (pricing).

Full head-to-head: PaidSync.ai vs the official Google Ads MCP.

Using Claude? See how to connect Google Ads to Claude, step by step. Also on Bing? See the Microsoft Ads MCP server.

What a Google Ads MCP server does

Three things. It reads, so the assistant pulls spend, conversions, Quality Score and search terms without an export. It writes, so campaigns, ad groups, keywords, ads, bidding, budgets, audiences and conversion actions can be created or changed from a chat. And it gates, so creates preview as a dry run first and destructive changes need an explicit confirm. Reading is table stakes across every Google Ads MCP in 2026. The depth of the write surface, MCC routing, and the honesty of the gating are where they differ.

Google Ads tools by category

The categories below hold 148 of the 158 tools, with named examples from the live tool registry. Some write to the account and the rest read from it. Connection and account-switching tools (connect_google_ads, set_active_account) sit outside the Google Ads list because they serve every platform. The full catalog is discoverable in any session through paidsync_context with include_tools:['google_ads'].

CategoryToolsExamples
Campaigns14create_search_campaign, create_shopping_campaign, create_demand_gen_campaign, pause_campaign, duplicate_campaign
Ad groups6create_ad_group, update_ad_group, pause_ad_group
Keywords and negatives17add_keywords, batch_add_negative_keywords, create_negative_keyword_list, research_keywords
Ads7create_responsive_search_ad, create_responsive_display_ad, pause_ad
Assets and extensions17add_sitelinks, add_callout_extensions, create_lead_form_asset, link_asset_to_campaign
Performance Max9create_performance_max_campaign, create_asset_group, add_asset_group_signal, get_pmax_insights
Shopping and product groups7subdivide_product_partition, exclude_product_partition, get_shopping_performance
Bidding and budgets12create_bidding_strategy, update_campaign_budget, set_device_bid_adjustment, get_budget_pacing
Targeting10set_geo_targeting, set_language_targeting, generate_reach_forecast
Audiences10create_custom_audience, upload_customer_match_list, add_audience_targeting, get_audience_insights
Conversions and imports9create_conversion_action, upload_offline_conversions, upload_conversion_adjustments
Experiments and labels10create_experiment, update_experiment, apply_label_to_campaign
Recommendations and change history4list_recommendations, apply_recommendation, get_change_history
Reporting8get_campaign_performance, get_keyword_performance, get_search_terms_report
Audits and analysis6run_account_audit, get_wasted_spend_report, analyze_search_term_ngrams, detect_anomalies
Raw API access2run_gaql_query, run_mutate

Four of these carry most of the operational weight. MCC routing (set_active_account switches the active customer) means one PaidSync connection covers every client account under the manager. Search-term analysis (analyze_search_term_ngrams, get_wasted_spend_report) turns a 10,000-row search-term report into a ranked negative-keyword list in one prompt. Performance Max tools read asset groups and signals for audits, then edit them from chat. And offline conversion imports keep Smart Bidding fed with real revenue when conversions live in a CRM, not on the website.

run_account_audit is also the engine behind the free Google Ads account audit, so you can see its scored report on your own account before you connect an AI client.

Set up in your AI client

Every client uses the same endpoint and the same Streamable HTTP transport. Paste it, sign in with your PaidSync login, and the Google Ads tools appear.

https://mcp.paidsync.ai/mcp

Prefer a key for read-only reports? A client that lets you set a header, such as Claude Code, can send it to the same URL as Authorization: Bearer ps_... or x-api-key. Never put the key in a URL; query strings end up in logs. Applying a change still requires the OAuth sign-in.

Claude

In claude.ai or the Claude Desktop app open Settings, then Connectors, search PaidSync, click Connect, and sign in with your PaidSync login. Connectors work on every Claude plan, including Free, which allows one custom connector. Step by step at connect Google Ads to Claude.

Claude Code

In your terminal run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp. Start a session, type /mcp, pick paidsync and sign in with your PaidSync login in the browser window that opens. Claude Code stores the OAuth token for you. For a team, commit a .mcp.json at the repo root with the same http server entry. Full walkthrough with prompts and headless runs: connect Google Ads to Claude Code.

ChatGPT

Open Plugins in the ChatGPT sidebar, select PaidSync.ai in the plugin directory and click Install plugin. Click Connect when asked and sign in with your PaidSync login. The plugin directory is on every ChatGPT plan, and what you can install depends on your plan and workspace. Step by step at connect Google Ads to ChatGPT.

Cursor

Add {"mcpServers": {"paidsync": {"url": "https://mcp.paidsync.ai/mcp"}}} to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project. Open Cursor Settings, then MCP, and sign in with your PaidSync login when Cursor prompts for OAuth. Windsurf uses the same shape with serverUrl in ~/.codeium/windsurf/mcp_config.json.

Gemini CLI

Run gemini mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp auth paidsync and sign in. Gemini Code Assist and Antigravity read the same ~/.gemini/settings.json with an httpUrl entry. The Gemini app takes one directly on a personal Google account under Custom apps for Spark; in Gemini Enterprise, Business edition, a team admin adds PaidSync under Connected apps. Step by step at connect Google Ads to Gemini.

Copilot Studio

In Copilot Studio open your agent, then Tools, Add a tool, New tool, Model Context Protocol. Paste the server URL, choose OAuth 2.0 with Dynamic discovery (or an API key sent as a Header named x-api-key), transport Streamable HTTP. Click Create, then Add to agent, and publish to the Microsoft 365 Copilot channel. Copilot Studio needs a work or school account. The consumer Copilot app does not accept custom MCP servers.

Run Google Ads from a chat window

A week on PaidSync's Google Ads stack looks like this. Monday morning you ask "what changed in the last 7 days, by campaign, and where is budget pacing off". The assistant pulls it from get_campaign_performance and get_budget_pacing and answers in plain numbers. You spot a Performance Max campaign leaking spend into a competitor's brand term, ask for a brand exclusion, review the proposed change, and confirm. Later you ask for an n-gram analysis of the last 30 days of search terms; the assistant returns the top loss-making n-grams, you pick five, and it adds them as campaign-level negatives after a second confirmation.

Because the same server carries Meta Ads, LinkedIn, TikTok, GA4, GTM, Search Console (read only), and Merchant Center, the follow-up question "did the Google Ads changes produce GA4 conversions and did the Merchant Center feed have any disapprovals last week" is answered in the same session, not in another tab. That cross-platform session is the practical difference between a Google Ads connector and a paid-media server. For prompt ideas, 15 Google Ads prompts for Claude is a working list, and the Google Ads audit guide shows the deeper account-review workflow.

When a number moves the wrong way, start with the Google Ads troubleshooting library. Each guide ranks the likely causes of one common problem and names the PaidSync tool that checks each cause.

Trust is the honest concern with write access, and the answer is procedural. In the PaidSync workspace every write is an approval card by default, and an applied card offers Undo when the change has a safe inverse. Over MCP, PaidSync writes no card, so your assistant's own confirmation prompt is the human check. On both paths creates preview first, destructive operations need an explicit confirm, and applied changes are logged, on a best-effort basis, with a 7-day before and after.

Connect a Google Ads account or an MCC to Claude, ChatGPT, or Cursor and run the first report in minutes.

Start free, 100 tasks, no card Read the category guide

The protocol surface behind the tools

PaidSync is one MCP endpoint covering 14 platforms; details on the MCP server page. To keep client context small, tools/list returns a lean starter set. The full catalog is discovered at runtime through paidsync_context, which returns the active customer, connected platforms, and the grouped tool catalog, and executed through paidsync_exec. That two-call pattern means an agent can enumerate and invoke every Google Ads tool without a 630+ tool schema payload sitting in every conversation.

Sign-in is OAuth 2.0 with dynamic client registration and PKCE, so no client ID is typed into any client. An API key is accepted for read-only use in an Authorization: Bearer or x-api-key header, never in the URL; applying a change requires the OAuth sign-in. Tokens are encrypted at rest with AES-256-GCM. MCC routing is first-class: set_active_account switches the active customer per task, and PaidSync manages the customer-ID header on every Google Ads API call. The server-side checks run whatever the client. Google Ads create tools default to dry_run for a no-op preview, destructive operations require confirm_destructive, and a pre-write validator blocks unsafe arguments. The approval step itself sits in the client: over MCP, PaidSync writes no card. For discovery, the domain publishes OAuth authorization-server and protected-resource metadata (RFC 8414 and RFC 9728), an MCP server card, agent-auth.json, security.txt, and a Content-Signal directive.

What this does not do

Stated plainly, because scoping a tool accurately beats overselling it.

  • Editor-style multi-object bulk uploads are not exposed as one call. A 200-change batch is 200 confirmed tasks or a scheduled Recommendation. Bulk campaign creation from a spreadsheet is not the shape of this tool set.
  • Google Ads scripts and Ads Editor CSV import are outside the API. They are outside the MCP too.
  • AI Max for Search follows Google's rollout. Availability on a given account matches what that account sees in Google Ads.
  • No approval card over MCP. In the PaidSync workspace every write waits as an approval card by default, and autonomy is opt-in per agent, inside budget guardrails you set. When your own assistant calls PaidSync over MCP, the human check is that assistant's confirmation prompt, so keep it on for write tools. Google Ads Recommendations are shown as Google's and applied one at a time; Google's own auto-apply stays off unless you subscribe to it with subscribe_to_recommendations.

Pricing

Every plan includes all 14 platforms and every MCC-linked client account; there is no per-account or per-platform charge. Every tool call counts as one task, whether it reads a report or drafts a change. Full detail at paidsync.ai/pricing.

PlanPriceIncluded
Free$0/mo100 tasks a month, no card required
ProFrom $99/mo1,000 tasks ($99), 2,500 tasks ($149), or 6,000 tasks ($199)
TeamFrom $249/mo10,000 shared tasks, up to 20 seats
Done For YouCustomFully managed paid media

Put Google Ads, MCC routing, and 13 more platforms in front of your AI assistant today.

Connect Google Ads to your AI

One setup per client, same endpoint and sign-in everywhere.

Add to ChatGPT: open PaidSync.ai in ChatGPT's plugin directory, install it, then sign in.

Add to Claude: open PaidSync.ai in Claude's connector directory, click Connect, then sign in.

Frequently asked questions

What is a Google Ads MCP server?

An MCP (Model Context Protocol) server exposes Google Ads API actions as typed tools that AI assistants like Claude, ChatGPT, and Cursor can call. A Google Ads MCP lets the assistant read spend, ROAS, and Quality Score, build campaigns, edit bidding, add negative keywords, and manage Performance Max through conversation instead of Google Ads Editor. PaidSync.ai's Google Ads surface has full write access and native MCC manager-account routing at https://mcp.paidsync.ai/mcp. Google's own official server is self-hosted and, since its 2 Nov 2026 release, also creates assets and manages labels with a propose-and-confirm step. See also the AI agent for Google Ads page.

Is there an official Google Ads MCP server?

Yes. Google's official Google Ads MCP server is open source and runs on your own machine or cloud, with your own Google Cloud project. Since release v0.0.6 of 2 Nov 2026 it has 7 tools, and its release notes say "Implement asset and label management with propose-and-confirm flow" (read 7 Nov 2026). PaidSync.ai is hosted, and its 158 Google Ads tools also build and change campaigns, budgets, bids and keywords.

What can PaidSync.ai's Google Ads tools do?

They read and change the whole account, inside a server of 630+ tools across 14 platforms. By category: campaigns, ad groups, keywords and negatives, ads, assets and extensions, Performance Max, Shopping and product groups, bidding and budgets, targeting, audiences, conversions and imports, experiments and labels, recommendations and change history, reporting, audits and analysis, and raw API access. From Claude, it creates Search, Performance Max, Display, Video, Shopping and Demand Gen campaigns.

Is PaidSync the only ads MCP with MCC manager-account support?

PaidSync ships MCC (My Client Center) routing as a native, one-connection feature: one PaidSync login covers every client account under the manager, and the assistant switches customer context per task with set_active_account. Google's official server leaves account selection to your own API credentials. The community servers we checked in September 2026 are single-account. For agencies with more than one client account, this is the practical difference between a demo and a production connection.

How is PaidSync different from Google's official Google Ads MCP?

Since its 2 Nov 2026 release, Google's official Google Ads MCP server also creates assets and manages labels, with a propose-and-confirm step before each change (read 7 Nov 2026). It exposes 7 tools and runs on your own machine with your own Google Cloud project and Google Ads API credentials. PaidSync is a hosted server: 158 Google Ads tools out of the box, MCC routing, full write access with a dry run before creates and an explicit confirm on destructive changes, OAuth 2.0 sign-in, and 13 more platforms in the same session (Meta, LinkedIn, TikTok, GA4, GTM, Search Console, Merchant Center, Snapchat, Reddit, Pinterest, Microsoft, X, ChatGPT Ads). Both can run side by side in the same MCP client. Detail at /vs/google-ads-mcp.

Is it safe to give an AI write access to a live Google Ads account?

PaidSync checks writes on every path, and the human step depends on where you work. In the PaidSync workspace every write is an approval card by default, and an applied card offers Undo when the change has a safe inverse. When Claude, ChatGPT or another assistant calls PaidSync over MCP, PaidSync writes no card, so the human check is your assistant's own confirmation prompt. On both paths, Google Ads create tools default to a dry_run preview that returns the exact planned change before anything touches the account, destructive tools (remove and pause tools, update tools with budget in their name, the raw mutate call) require an explicit confirm_destructive step, and applied changes are logged, on a best-effort basis, with a 7-day before and after. Sessions can be revoked at any time, and tokens are encrypted at rest with AES-256-GCM. Read operations change nothing.

What does PaidSync's Google Ads tool set not cover?

AI Max for Search follows Google's own rollout, so availability on a given account matches what that account sees in Google Ads. Editor-style multi-object bulk uploads are not exposed as a single call; a 200-change edit is 200 confirmed tasks or a scheduled Recommendation action. Google Ads scripts and Ads Editor CSV import are outside the API surface entirely, so they are outside the MCP too.

How much does the PaidSync Google Ads MCP cost?

Free is $0 for 100 tasks a month with no card. Pro starts at $99/mo for 1,000 tasks, with 2,500 tasks at $149 and 6,000 at $199. Team starts at $249/mo for 10,000 shared tasks and up to 20 seats. Done For You is custom-priced fully managed paid media. Every plan includes all 14 platforms and every MCC-linked client account; there is no per-account or per-platform charge. Google's own MCP server is free; the cost is the engineering to run it.

Which AI assistants work with the PaidSync Google Ads MCP?

Claude (web, desktop, and Claude Code), ChatGPT, Cursor, Windsurf, Gemini CLI, Perplexity, Copilot Studio, and any client that speaks MCP over Streamable HTTP. The Gemini app takes PaidSync on a personal Google account under Custom apps for Spark; the consumer Copilot app does not accept custom MCP servers. Connection guides for Google Ads: Claude, ChatGPT, Gemini, Perplexity, Copilot.

What is the best Google Ads MCP for Claude?

For Claude, PaidSync.ai is a hosted Google Ads MCP that reads reports and makes changes on the official Google Ads API, with no developer token or Google Cloud project. Add it from Claude's connector directory and sign in with Google. Creates run as a dry run first, and new Search campaigns start paused. It is free for 100 tasks a month.