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 7a40eae

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.

Connects to: Google Ads (Google Ads API)
Access: query only (GAQL search); no mutate service exposed
Tools: 3, all read

Connect

pipx run google-ads-mcp   # then add it to your MCP client with GOOGLE_PROJECT_ID and GOOGLE_ADS_DEVELOPER_TOKEN in env

Run this in a terminal inside your project folder. Claude Code, Cursor and Codex then read the skill from where it lands.

Requires

a developer token with Explorer access or better
the Google Ads API enabled in a Google Cloud project
Application Default Credentials with the adwords scope, or the OAuth proxy
pipx (Python)

Safety review of the skill text and its scripts
Network	yes	Calls the Google Ads API. The README notes Google adds a usage header to your calls to collect product usage data.
Shell	no	None exposed.
Secrets	yes	Developer token and credentials in environment variables; the OAuth proxy option encrypts stored tokens.
Deletes	no	No mutate tool. The README’s first note stands: the server exposes your data to whatever agent you connect.

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

How to install these skills: three routes into Claude Code, and one line to check they loaded.

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 inputs

Questions

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, and the README marks it optional for setups that already carry one. Production accounts need at least Explorer access; a new token may be upgraded to Explorer automatically, and if it is not, the README links the application in the API Center.

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.