An AI agent for Google Ads reads your account, finds what to fix and makes the change for you. PaidSync.ai is one: it uses the official Google Ads API, so Claude or ChatGPT can pull reports and change budgets, bids, keywords and campaigns in plain language, with no developer token, no Google Cloud project and nothing to host. In the PaidSync.ai workspace, ready-made Ads Agents such as Wasted Spend Hunter run on a schedule and send each change as an approval card. Campaign creates run as a dry run first, and new Search campaigns start paused. The same connection covers Meta, TikTok, LinkedIn and 10 more platforms. PaidSync.ai is free for 15 tasks a month, with no card needed.
Every control, and what is not built yet, is listed on the secure Google Ads MCP server page.
Google publishes a free, open-source Google Ads MCP server that you host yourself. Its README on GitHub, checked on 16 October 2026, lists three tools (a search tool for Google Ads queries, a lookup for resource metadata and a list of the accounts your login can reach) and five setup steps: configure Python, configure a developer token, enable APIs in your Google Cloud project, configure credentials and configure your MCP client. It suits a developer who wants to host the code and read data.
PaidSync.ai is the hosted option for people who want Claude to act on the account. What you can check:
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.
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.
The categories below come from the live tool registry, and each tool is named. 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'].
| Category | Tools | Examples |
|---|---|---|
| Campaigns | 14 | create_search_campaign, create_shopping_campaign, create_demand_gen_campaign, pause_campaign, duplicate_campaign |
| Ad groups | 6 | create_ad_group, update_ad_group, pause_ad_group |
| Keywords and negatives | 17 | add_keywords, batch_add_negative_keywords, create_negative_keyword_list, research_keywords |
| Ads | 7 | create_responsive_search_ad, create_responsive_display_ad, pause_ad |
| Assets and extensions | 17 | add_sitelinks, add_callout_extensions, create_lead_form_asset, link_asset_to_campaign |
| Performance Max | 9 | create_performance_max_campaign, create_asset_group, add_asset_group_signal, get_pmax_insights |
| Shopping and product groups | 7 | subdivide_product_partition, exclude_product_partition, get_shopping_performance |
| Bidding and budgets | 12 | create_bidding_strategy, update_campaign_budget, set_device_bid_adjustment, get_budget_pacing |
| Targeting | 10 | set_geo_targeting, set_language_targeting, generate_reach_forecast |
| Audiences | 10 | create_custom_audience, upload_customer_match_list, add_audience_targeting, get_audience_insights |
| Conversions and imports | 9 | create_conversion_action, upload_offline_conversions, upload_conversion_adjustments |
| Experiments and labels | 10 | create_experiment, update_experiment, apply_label_to_campaign |
| Recommendations and change history | 4 | list_recommendations, apply_recommendation, get_change_history |
| Reporting | 9 | get_campaign_performance, get_keyword_performance, get_search_terms_report, get_auction_insights |
| Audits and analysis | 6 | run_account_audit, get_wasted_spend_report, analyze_search_term_ngrams, detect_anomalies |
| Raw API access | 2 | run_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.
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/mcpPrefer 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.
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.
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.
Open Settings, then Security and login, and turn on Developer mode. Go to chatgpt.com/plugins, click the plus button, name the app PaidSync, paste the server URL and choose OAuth. Sign in with your PaidSync login the first time a tool runs. Developer mode is available on Plus, Pro, Business, Enterprise and Education plans on the web. Step by step at connect Google Ads to ChatGPT.
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.
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.
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.
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, 15 tasks, no card Read the category guidePaidSync 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.
Stated plainly, because scoping a tool accurately beats overselling it.
subscribe_to_recommendations.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.
| Plan | Price | Included |
|---|---|---|
| Free | $0/mo | 15 tasks a month, no card required |
| Pro | From $99/mo | 600 tasks ($99), 1,200 tasks ($149), or 4,000 tasks ($199) |
| Team | From $249/mo | 5 seats, 6,000 shared tasks |
| Done For You | Custom | Fully managed paid media |
Put Google Ads, MCC routing, and 13 more platforms in front of your AI assistant today.
One setup per client, same endpoint and sign-in everywhere.
An AI agent for Google Ads is software that reads your account, decides what needs fixing and carries the change out, instead of only advising. PaidSync.ai does this through Claude, ChatGPT and Cursor, which can read spend, ROAS and Quality Score, build campaigns, edit bidding and add negative keywords. Its Ads Agents in the PaidSync.ai workspace do the same on a schedule, and by default every change waits as an approval card. Full write access and MCC manager-account routing run at https://mcp.paidsync.ai/mcp.
Yes. Google's official Google Ads MCP server is open source and read-only, has 3 tools, and runs on your own machine or cloud (release 0.0.4, 25 Sep 2026; checked 29 Sep 2026). PaidSync.ai is hosted, and its Google Ads tools also build and change campaigns.
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.
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 is read-only and 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.
Google's official Google Ads MCP server is strictly read-only, exposes 3 tools, and runs on your own machine with your own 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.
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.
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.
Free is $0 for 15 tasks a month with no card. Pro starts at $99/mo for 600 tasks, with 1,200 tasks at $149 and 4,000 at $199. Team starts at $249/mo for 5 seats and 6,000 shared tasks. 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.
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.
PaidSync.ai is a hosted AI agent for Google Ads 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 15 tasks a month.