Vendor-authored, source-reviewed comparison · 2026
Best Google Ads MCP servers, compared on limits, tools, and real write depth
The useful comparison starts with monthly operations, Google Ads-specific tool count, and whether supplied image or video assets can actually be changed. Setup, account routing, approval, and recovery still matter once the tool reaches a live account.
- Published
- · Aug 21, 2026
- Last verified
- · August 21, 2026
- Products reviewed
- · 6
- Author
- · NotFair product team
Our verdict
Best for operators who want AI to safely change Google Ads—not merely report on it
NotFair combines deep Google Ads coverage with approval-gated execution, post-change impact review, and supported reversals.
- Monthly operations
- 300 free
- After 7 unlimited days
- Google Ads tools
- 117
- Reads and writes
- Creative assets
- Images + video links
- Supplied images and YouTube IDs
- Write lifecycle
- Approval → impact → undo
- Accountable changes
Comparison matrix
Capacity and creative control first
“Unlimited tools” and “creative support” are too vague to buy against. This table separates monthly call capacity, Google Ads-specific tool breadth, image handling, and video handling. “Not published” means the vendor’s public documentation does not support a more specific claim.
| Server | Operations / month | Google Ads tools | Change image assets | Change video assets | Write access |
|---|---|---|---|---|---|
NotFair Recommended for accountable writes | Free: 300/month after 7 unlimited days. Growth: unlimited.Usage source | 117 Google Ads tools | Yes — upload, link, unlink, and replace supplied images across Search, Display, and Performance Max workflows.Creative source | Partial — create campaigns and asset links from existing YouTube video IDs; NotFair does not upload video files to YouTube. | Yes — campaigns, bids, budgets, keywords, ads, assets, and more |
Google official | No MCP subscription cap; self-hosted usage remains subject to Google Ads API quotas. | 3 tools | No — current release is read-only. | No — current release is read-only. | No — current public tool surface is read-only |
Markifact | 200 one-time signup credits; paid plans use a selected monthly credit balance. Most MCP data operations cost about 1 credit.Usage source | Google-specific count not published; 1,000+ operations across 30+ marketing platforms | Vendor documents Google Ads asset writes, but does not publish a Google-specific image mutation inventory.Creative source | Google-specific video upload or replacement scope is not publicly documented. | Yes — broad cross-platform marketing actions |
Ryze AI | Free to connect; no public monthly MCP operation cap is stated. Paid Ads Autopilot starts at $89/month.Usage source | 150+ tools across Google Ads, Meta Ads, and other connected platforms; Google-specific count not published | Vendor says creatives are programmable; Google-specific image upload or replacement details are not published.Creative source | Google-specific video upload or replacement details are not published. | Yes |
Adspirer | Free 15; Plus 150; Pro 600; Max 3,000 tool calls/month.Usage source | 60+ Google Ads tools on the current integration page | Yes — supplied image URLs can be validated, uploaded, reused, and changed in supported Display and Performance Max workflows.Creative source | Partial — supported in Display creative updates and through existing YouTube video IDs; it does not generate videos. | Yes — campaigns, budgets, targeting, and supported creative changes |
FGRibreau / mcp-google-ads | No software subscription cap; self-hosted usage remains subject to Google Ads API quotas. | 50 tools in the current README | Yes — upload a base64 image asset. | No dedicated video upload or replacement tool is documented. | Yes — preview followed by confirm-and-apply |
Asset support means working with supplied advertising assets, not generating the underlying image or video. Google Ads video workflows commonly require an existing YouTube video ID because the Google Ads API does not upload a source file to YouTube.
Operating model
Setup, safeguards, account routing, and client reach
| Server | Best for | Delivery | Credentials | Safety lifecycle | Multi-account | Clients |
|---|---|---|---|---|---|---|
NotFair Recommended for accountable writes | Operators who want to diagnose and safely ship changes | Hosted remote MCP | Hosted OAuth; no customer developer token | Exact proposal, explicit approval, provenance, impact review, undo metadata | Manager-account discovery and explicit per-call account routing | Claude Web/Code, Codex CLI, Cursor, OpenClaw, Hermes |
Google official | Developers who want a first-party, read-only server | Self-hosted | Your Cloud project, OAuth credentials, and developer token | No mutation surface to guard | Lists directly accessible customers; infrastructure is yours to maintain | Any client that can run a local MCP server |
Markifact | Cross-platform marketing workflows | Hosted remote MCP | Hosted connection; no customer developer token | Vendor documents approval before writes | Unlimited ad accounts on current paid plans | Claude, ChatGPT, Codex, Cursor, and other MCP clients |
Ryze AI | Teams wanting one hosted connector across ads and analytics | Hosted remote MCP | Hosted OAuth; no customer developer token | Vendor documents approval controls, dry-run mode, and change limits | Vendor advertises MCC support and per-client isolation | Claude, ChatGPT, and other MCP-compatible clients |
Adspirer | Multi-platform campaign creation with explicit tool-call plans | Hosted remote MCP + ChatGPT App | Hosted OAuth; no customer developer token | Research → validate → confirm workflow; paused-first creation | Connected-account selection with MCC support | ChatGPT, Claude, Codex, Cursor, OpenClaw |
FGRibreau / mcp-google-ads | Developers who want an open-source read/write server | Self-hosted open source | Your Google Ads developer token and OAuth setup | Preview/confirm, dry-run default, budget caps, and bid limits | Lists accessible accounts; target is configured by customer ID | MCP tool callers that can run the local binary |
NotFair is the publisher of this comparison and is therefore not a neutral party. The methodology and source links are public so buyers can challenge any row. Vendor-wide tool totals are not treated as Google Ads-specific totals.
Testing method
A benchmark that can be rerun
We review the connection boundary, tool surface, write contract, account routing, and recovery path. Marketing claims without a public document, schema, or observable flow are not treated as verified capabilities.
01
Monthly capacity
How many MCP operations can the user run each month, what consumes quota, and what happens at the limit?
02
Tool depth
How many tools are Google Ads-specific rather than a cross-platform total, and which workflows do they actually cover?
03
Creative assets
Can the server upload, link, replace, or unlink supplied image and video assets—not merely generate ad copy?
04
Connection
Can a non-developer connect without building OAuth infrastructure or waiting for a developer token?
05
Useful reads
Can the agent inspect accounts, performance, search terms, settings and change history with typed outputs?
06
Safe writes
Are mutations previewed, bound to explicit approval and protected by server-side guardrails?
07
After the write
Can the operator identify provenance, review impact and reverse supported changes?
08
Agency routing
Can the agent discover and explicitly target a client beneath a manager account?
09
Client reach
Does the same remote endpoint work in the AI workspace the operator already uses?
Test boundary
NotFair was verified against its production endpoint in Claude Code and Codex CLI on both the apex and www origins, including OAuth issuer matching and an authenticated MCP request. Competitor rows are document- and source-code-based unless their own linked methodology says otherwise. No competitor account was connected and no competitor write was executed for this review.
Decision guide
Choose by operating model
Choose NotFair
You want a hosted endpoint, live reads, approval-gated writes, MCC routing, change provenance, impact review, and supported reversals.
Choose Google’s official server
You want first-party read-only reporting, already have Google Ads API credentials, and prefer to own the runtime.
Choose a cross-platform suite
You value the breadth of one connection across many ad and marketing platforms more than depth in the post-write lifecycle.
Choose open source
Your engineers want to inspect and customize every tool, and your team is comfortable operating OAuth, secrets, API versions, and guardrails.
NotFair production path
Inspect → diff → approve → execute → measure → undo
- The agent reads live account state and freshness metadata.
- A proposed write shows the target and intended change.
- Execution waits for explicit user approval.
- The operation records its author, ID, timestamp, and provenance.
- Impact review compares the before/after window.
- Supported mutations keep inverse-operation metadata for reversal.
Remote endpoint
https://notfair.co/api/mcp/google_adsPublic verification prompts
Use the same nine prompts on every server
Show my plan, monthly operation limit, operations used, and operations remaining.
List every Google Ads-specific tool available in this connection; exclude tools for other platforms.
Can you upload and replace supplied image and video assets? Show the exact tools and limitations for each format.
List every accessible account and identify which are manager versus client accounts.
Audit the last 30 days and show the evidence behind the three highest-impact problems.
Propose negative keywords, including scope, match type, and the exact search-term evidence.
Show the exact diff before changing a budget. Do not execute until I approve.
After the write, return the operation ID, author, timestamp, and verification result.
Review the change’s impact and show the supported reversal before undoing anything.
Google Ads MCP server FAQ
Direct answers for buyers comparing hosted and self-hosted options.
There is no universal winner. Use Google's official server for first-party, self-hosted, read-only reporting. Use NotFair when you want a hosted connection, manager-account routing, approval-gated writes, impact review, and undo metadata. Evaluate Markifact or Adspirer when broad cross-platform coverage is the main requirement.
Hosted services such as NotFair, Markifact, Ryze AI, and Adspirer handle the Google Ads API plumbing behind their OAuth flow. Google's official server and self-hosted community servers require you to supply and maintain your own Google Ads credentials and developer token.
Some can. Google's current official public server is read-only. NotFair and several hosted or community alternatives expose write tools. For production accounts, compare the full safety lifecycle: preview, exact approval, server-side limits, audit provenance, post-change impact review, and a practical reversal path.
NotFair includes 300 operations per month on Free after seven unlimited days, while Growth is unlimited. Adspirer publishes caps of 15, 150, 600, or 3,000 monthly calls by plan. Markifact uses credits, with most MCP data operations costing about one credit; its paid monthly balance depends on the selected package. Self-hosted servers do not impose a SaaS plan cap but remain subject to Google Ads API quotas. Ryze AI does not publish a monthly MCP operation cap on its current connector page.
Capability varies. NotFair can upload supplied images and change their serving links; for video it works with existing YouTube video IDs rather than uploading video files to YouTube. Adspirer documents supplied-image uploads and supported Display creative changes, with video supplied through existing URLs or YouTube IDs. FGRibreau documents image upload but no dedicated video tool. Google's official server is read-only. Markifact and Ryze AI advertise creative operations, but their public Google-specific image and video mutation contracts are not detailed enough to claim complete support.
Yes. NotFair discovers eligible client accounts beneath manager accounts and supports explicit account routing per call, so an agent can identify the intended client before reading or staging a write.
No. This review combines public documentation and current tool descriptions with live production verification of NotFair. Competitor behavior is labeled from vendor documentation or public source code; we do not claim a live-account test where one was not performed.
From comparison to first write
Connect once. Audit first. Approve only what you understand.
The free plan includes seven days of unlimited access, then 300 MCP operations each month. No credit card and no customer developer token.