136 live tools for Google Ads, native MCC manager-account routing, every write held for your confirmation, inside the same server that runs Meta, LinkedIn, TikTok, GA4, and GTM. Compared honestly against Google's own reference MCP and the leading community servers.
PaidSync is a Google Ads MCP server with full write access. It gives Claude, ChatGPT, and Gemini 133 Google Ads tools, from campaign creation and Performance Max asset updates to bidding, negatives, and offline conversion imports, with every change held for your confirmation before it touches the account. Free at $0 for 15 tasks a month, Pro from $99/mo, native MCC routing for agencies, and the same connection also covers Meta, LinkedIn, TikTok, GA4, GTM, and 7 more platforms.
An MCP server turns an ad platform's API into typed tools an AI assistant can call. Connect one to Claude or ChatGPT and "pause every keyword with a cost per conversion above $80 and CTR under 2%" becomes something the assistant can check, propose, and, once you approve, execute. This page covers PaidSync's Google Ads surface in full: what the 136 tools do, how MCC routing works for agencies, how the approval gates work, what the server deliberately does not do, and how it compares with Google's own reference MCP and the community options.
It is written for both halves of that audience. Marketers who want to run Google Ads from a chat window, and agent builders who want to know exactly what the protocol surface looks like before wiring it into a workflow. Each section is labeled.
What a Google Ads MCP server does
Three things, in practice. It reads, so the assistant can pull spend, conversions, Quality Score, and search term reports without you exporting from the UI. It writes, so campaigns, ad groups, keywords, ads, bidding, budgets, audiences, and conversion actions can be created or changed from conversation. And it gates, so nothing the AI proposes runs until a human confirms it. The reading part is table stakes across every Google Ads MCP available in 2026. The depth of the write surface, the presence of MCC routing, and the honesty of the gating are where they differ.
All 133 Google Ads tools by category
PaidSync's live server exposes 133 Google Ads tools (server total 440+ across 14 platforms). The table below names the operational core; the full current catalog is discoverable live from any session via paidsync_context with include_tools:['google_ads'], described in the agent-builder section.
| Category | Named tools |
|---|---|
| Account and MCC routing | connect_google_ads, list_accounts, list_google_ads_accounts, set_active_account |
| Campaign lifecycle | list_campaigns, create_search_campaign, create_shopping_campaign, update_campaign, pause_campaign, enable_campaign, duplicate_campaign |
| Ad groups | list_ad_groups, create_ad_group, update_ad_group, pause_ad_group, enable_ad_group |
| Keywords and negatives | list_keywords, add_keywords, pause_keyword, remove_keyword, add_negative_keywords, batch_add_negative_keywords, create_negative_keyword_list, apply_negative_keyword_list |
| Search terms | get_search_terms_report, analyze_search_term_ngrams, get_wasted_spend_report |
| Ads and assets (RSAs, extensions) | list_ads, create_responsive_search_ad, create_responsive_display_ad, pause_ad, list_assets, add_sitelinks, add_callout_extensions, add_structured_snippets, link_asset_to_campaign |
| Performance Max | create_performance_max_campaign, list_asset_groups, create_asset_group, update_asset_group, add_asset_group_asset, add_asset_group_signal, get_pmax_insights |
| Bidding and budgets | list_bidding_strategies, create_bidding_strategy, update_bidding_strategy, set_device_bid_adjustment, update_campaign_budget, get_budget_pacing |
| Audiences | list_audiences, list_user_lists, create_custom_audience, upload_customer_match_list, add_audience_targeting, get_audience_insights |
| Conversions and imports | list_conversion_actions, create_conversion_action, setup_google_ads_conversion, upload_offline_conversions, upload_conversion_adjustments, get_conversion_tracking_status |
| Experiments and drafts | list_experiments, create_experiment, update_experiment, list_campaign_drafts |
| Recommendations and change history | list_recommendations, apply_recommendation, get_change_history |
| Reporting and pacing | get_campaign_performance, get_keyword_performance, get_performance_by_conversion_actions, get_quality_score_report, get_auction_insights, get_account_summary |
| Audits | run_account_audit, get_wasted_spend_report, get_account_health_score, get_conversion_tracking_status |
Four of these carry most of the heavy operational work. MCC routing (list_accounts walks the manager tree, set_active_account switches context) means one PaidSync connection covers every client account under the manager, and the assistant switches customer context per task. This is the practical differentiator versus every other Google Ads MCP surveyed for this page. Search-term intelligence (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 their signals for PMax audits, then let you edit asset groups and audience signals from chat. And offline conversion imports (upload_offline_conversions) keep Smart Bidding fed with real revenue for the businesses whose conversions live in a CRM, not on the website.
Run Google Ads from a chat window
The practical shape of 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 whose search-category report shows spend leaking into a branded competitor term you never wanted; you 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 (69 tools), LinkedIn (25), TikTok (13), GA4 (28), GTM (37), Search Console (6), and Merchant Center (15), the follow-up question "did the Google Ads changes actually 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. If you want prompt ideas, 15 Google Ads prompts for Claude is a working list, and the Google Ads audit guide shows the deeper account-review workflow.
Trust is the honest concern with write access, and the answer is procedural, not promissory. Nothing applies without your confirmation, previews show the exact planned change first, and destructive operations require a second explicit confirmation. When PaidSync opened paid plans in May 2026, six agencies became paying customers within four days, and the approval gate was the feature they cited most.
Connect a Google Ads account or an MCC to Claude, ChatGPT, or Gemini and run the first report in minutes.
Start free, 15 tasks, no card Read the category guideThe protocol surface behind the 136 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 (include_tools:['google_ads'] returns the exact Google Ads tool names), and executed through paidsync_exec. That two-call pattern means an agent can enumerate and invoke all 133 Google Ads tools without a 460+-tool schema payload sitting in every conversation.
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. Safety is enforced server-side, not left to the client. Writes are approval-gated, most mutation tools accept dry_run for a no-op preview of the planned change, and destructive operations require confirm_destructive. Sessions can be revoked at any time. For discovery and verification, 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, so an agent can establish what this server is and how to authenticate against it before the first task.
Google's official Google Ads MCP, compared honestly
Google ships an MCP reference for the Google Ads API. It is Google-only, read-focused, and aimed at engineering teams that want to extend it. The write endpoints of the Google Ads API are all reachable through it, but the tool layer, the MCC routing UX, the audit layer, and the multi-platform session are things you build yourself. That is a valid choice for a team with engineering capacity and a preference for owning the stack. It is not the same product as a managed server. Full head-to-head at PaidSync vs official Google Ads MCP.
Two community servers show up on most current Google Ads MCP listings. cohnen/mcp-google-ads is a popular open-source Google Ads MCP focused on reporting; it is Google-only, self-hosted, and does not include an approval-gate layer or MCC routing UX. AdKit's Google Ads MCP is a hosted three-platform server (Google, Meta, LinkedIn) at $29 to $49 per year; writes apply immediately when the AI calls the tool, without a confirmation step. The comparison below uses each vendor's public pages as of August 2026.
| Dimension | PaidSync | Google official MCP | cohnen/mcp-google-ads | AdKit |
|---|---|---|---|---|
| Google Ads tools | 136 | Whatever you build on the API | Reporting-focused subset | Subset of 23 total |
| Write access | Full, gated | API surface, you build it | Read-focused | Yes, ungated |
| MCC manager-account routing | Yes, native | API supports it, no UX | Single account | Not listed |
| Approval gates on writes | Yes, every write held for confirmation | You implement it | Not applicable | No, applies immediately |
| Hosted vs self-hosted | Hosted, connect and go | Self-hosted, engineering setup | Self-hosted, run it yourself | Hosted |
| Platform scope in same session | 14 platforms (Meta, LinkedIn, TikTok, GA4, GTM, GSC, Merchant Center, and more) | Google Ads only | Google Ads only | Google, Meta, LinkedIn |
| Audit layer (wasted spend, PMax insights, n-grams) | Yes, named tools | Build it | No | Not listed |
| Google Partner status | Google Premier Partner (founder, top 3% globally) | Google, first party | Not applicable | Not listed |
| Price | Free $0 (15 tasks), Pro from $99/mo | Free, API quota applies | Free, self-hosted | $29 to $49 annual |
Quick verdict.
You have engineering capacity and want to own the stack: Google's official MCP reference. Canonical, predictable, and free.
You want a free, self-hosted Google Ads MCP for personal reporting: cohnen/mcp-google-ads. Widely used, well-scoped for read work.
You run only Google, Meta, and LinkedIn on one account and want the cheapest hosted option: AdKit at $29 annual. Accept ungated writes.
You run more than one Google Ads account (agency, MCC), want approval gates, or need Google alongside GA4, GTM, or another ad platform in the same session: PaidSync. One connection covers the MCC, one session covers the stack, and every write is held for confirmation.
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 is subject to Google's rollout. Availability on a given account matches what that account sees in Google Ads.
- No unattended spend. Every write waits for your confirmation. If you want an AI that changes live budgets without a human tap, this is deliberately not that. If you want the closer thing to autonomy, use
create_experimentandapply_recommendationwhere Google itself gates the change.
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.
| 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 133 Google Ads tools, MCC routing, and the other 13 platforms in front of your AI assistant today.
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 Gemini 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's Google Ads surface is 136 tools with full write access and native MCC manager-account routing. Google's own reference MCP is read-focused and aimed at engineers extending it themselves.
How many Google Ads tools does PaidSync have?
136 live Google Ads tools, inside a server of 460+ tools across 14 platforms. The Google Ads set covers customer and MCC routing, every campaign type (Search, Performance Max, Display, Shopping, Video, App, Demand Gen), ad groups, keywords with match types and negatives, responsive search ads, extensions (assets), bidding strategies including portfolio bidding, audiences (customer match, similar, in-market, custom), conversions and offline conversion imports, experiments and drafts, labels, budgets and budget orders, recommendations, change history, and full performance reporting with breakdowns by campaign, ad group, keyword, search term, geography, device, network, time, and audience.
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. As of August 2026, no other ads MCP surfaced in the current Google Ads MCP category listings ships MCC routing as a first-class connected feature. Google's official MCP exposes the API surface (which supports MCC) but leaves the routing UX to whoever extends the reference. Community MCP servers such as cohnen/mcp-google-ads and Composio's Google Ads connector are single-account-focused. 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?
Google's reference MCP is Google-only, read-focused, and requires an engineer to wire it into an AI client, manage OAuth and quota, and build the tool layer on top. PaidSync is a managed server: 136 named Google Ads tools out of the box, MCC routing, full write access with an approval gate on every mutation, and 12 more platforms in the same session (Meta, LinkedIn, TikTok, GA4, GTM, Search Console, Merchant Center, Snapchat, Reddit, Pinterest, Microsoft, 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 never applies a change without your confirmation. Every write is approval-gated in chat, most mutation tools support a dry_run preview that returns the exact planned change before anything touches the account, and destructive operations (delete campaign, remove asset) require an explicit confirm_destructive step. Sessions can be revoked at any time. Read operations run without confirmation because they change nothing.
What does PaidSync's Google Ads tool set not cover?
AI Max for Search campaigns (announced at I/O 2026) is in staged rollout across accounts; the MCP tracks 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 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 reference 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, Gemini, Perplexity, Cursor, Windsurf, and any client that speaks MCP. Connection guides for Google Ads specifically: Claude, ChatGPT, Gemini, Perplexity, Copilot.