TOOLKIT
Google Ads MCP
Google’s official MCP server for the Google Ads API: three query tools and four reference resources, gated by a developer token and OAuth, with a YAML file to switch tools off.
by Google (official)googleads/google-ads-mcpApache-2.0 licence932 starscommit 7a40eaeread by us 11 September 2026
Three tools: `search` (a GAQL query against an account), `get_resource_metadata` (what fields a resource such as campaign carries), and `list_accessible_customers`. Four resources for the agent to read: the API discovery document, the metrics list, the segments list, and the release notes.
Access is by query. The `search` tool runs GAQL, which is read-only in the Google Ads API; mutations go through separate services this server does not expose. `tools_config.yaml` lets you disable tools or namespaces entirely.
The gate is Google’s: a developer token with at least Explorer access for production accounts, the Google Ads API enabled in a Cloud project, and either Application Default Credentials or the FastMCP OAuth proxy for multi-user setups.
What it exposes
3 tools, and which ones change things
All tools: search get_resource_metadata list_accessible_customers
Resources: discovery-document metrics segments release-notes
Writes
None. There is no tool in this server that changes your data.
Pairs with
Skills that work on what it reads
- adsPaid campaign strategy across Google, Meta, LinkedIn, TikTok and X, with the account decisions (kill, keep, scale, budget) routed to fourteen playbooks and guarded by an audit rulebook.
- ads-performance-analyticsHow to read a paid-media dashboard without fooling yourself: platform reporting quirks, seven attribution models, multi-platform reconciliation, the ROAS-versus-LTV trap, statistical noise, incrementality, and twelve interpretation failures.
- attributionWhich channel caused the sale: seven models and how each one lies, three measurement paradigms, reconciliation of platform, analytics and CRM numbers, and a first-party build track for stitching bookings to their source.
Method behind it
Our guide to how Google Ads works names the fields worth querying first: search terms, impression share, conversion lag. A GAQL query through this server is how an agent reads them without a spreadsheet.
How Google Ads works: the six auction inputsQuestions
Questions people ask before installing
Can the agent change bids or pause campaigns?
Not through this server. GAQL is a read language; the mutate services are not wired in. For drafted changes with approval gates, see claude-ads on this shelf.
Why does it need a developer token?
Every Google Ads API caller does. A new token starts at test-account access; Explorer access is needed for production accounts and the README links the application.
Can I hide some tools?
Yes. `tools_config.yaml` enables or disables tools and namespaces and renames their prefixes; a missing or invalid file makes the server refuse to start rather than run open.