Google Ads MCP Unofficial
Related Servers
Alternatives to Google Ads MCP Unofficial
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables management of Google Ads accounts via MCP, providing read and write tools for campaigns, ad groups, keywords, assets, and more, with support for reporting and mutations.-
- AlicenseNot gradedqualityCmaintenanceMCP server for managing Google Ads campaigns through the official Google Ads API, covering accounts, campaigns, budgets, keywords, search terms, and keyword ideas. It provides tools for both reading and mutating live ads data, such as pausing campaigns, updating budgets, and adding keywords.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to report on and manage Google Ads accounts, including GAQL queries, performance metrics, search terms, budgets, and campaign management.214 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that enables safe, audited mutation of Google Ads campaigns—creating ads, ad groups, keywords, and assets or adjusting budgets and statuses—with a dry-run default and an optional guarded remove operation, plus read-only Keyword Planner ideas.221MIT
- AlicenseAqualityCmaintenanceMCP server to read and manage Google Ads accounts via GAQL queries, campaign/ad group/keyword operations, and safe write support with draft-confirm flow.1638 npmMIT
- AlicenseAqualityBmaintenanceMulti-user Google Ads MCP server with OAuth-per-user auth, Firestore token storage, raw GAQL queries, and 10+ extra reporting tools beyond the official server.131MIT
TDQS
Scored across 30 tools
Most tools target a distinct resource and action, especially the core list/get/set/pause/resume cluster. The main ambiguity is among the meta/utility tools (capabilities, data_inventory, agent_manifest, connection_status, privacy_audit) which all describe capabilities or state without touching Google Ads. Overall an agent can usually tell them apart thanks to clear scoping.
The core Google Ads tools follow a predictable verb_noun pattern (list_campaigns, get_campaign, pause_keyword, set_keyword_bid_micros). However, the utility block breaks this with noun-only names like data_inventory, capabities, agent_manifest, connection_status, and onboarding, and profile_get/profile_update use noun_verb order. The mix is readable but not fully consistent.
At 30 tools, this exceeds the 25+ threshold and feels heavy for the server's core purpose. Several meta/status/profile/cache tools (inventory, capabities, manifest, connection_status, privacy_audit, cache_status, onboarding, profile_get/profile_update) could be consolidated or moved elsewhere. The broad Google Ads surface explains some of the count, but the set would be tighter with fewer support utilities.
The server covers the core read/analyze/mutate workflow well: list and get campaigns, ad groups, and keywords, performance reports, waste/quick-win analysis, and gated bid/budget/status mutations. Obvious gaps include creating/deleting campaigns, ad groups, or keywords, ad-group-level performance metrics, and a broader campaign update surface. Agents can complete many optimization flows but may hit dead ends for lifecycle management.