Connect Claude Code to Google Ads through Google's MCP server, disable its write tools, and request a four-phase account audit. The five-file pack includes an optional Performance Max review. Report coverage depends on the data available through your connection.

This guide covers a local stdio connection in Claude Code with Application Default Credentials (ADC). One prompt can trigger several queries and analysis phases. It does not mean one API call or a fixed runtime.

What is the Google Ads MCP server?

The Google Ads MCP server connects an AI client to the Google Ads API. You run the local server on your computer. Cloud Run deployment is an optional alternative, outside this setup.

The server includes reporting tools and tools that create assets or manage labels. This guide disables the asset and label tools for an audit-only setup. A person reviews the report and applies account changes separately.

When enabled, write tools use a propose-and-confirm process before submitting changes. That process does not make an installation read-only. The configuration below limits this server's tools. It does not disable unrelated tools or scripts in Claude Code.

We reviewed v0.0.6, released November 2, 2026. Its commit is 7452a9d49e3d350403f2610cd7125c60f6d05264. The setup pins that commit. Dependencies still follow the release's version ranges.

Google's integration page, dated October 30, describes a read-only server. The later release includes write tools. This guide follows the selected release's configuration and tool definitions.

What do I need before starting?

Requirement What to check
Google Ads account with data The Google user you authenticate must have access
Google Cloud project Use the project that owns your OAuth client
Google Ads API access Production accounts require Explorer, Basic or Standard access
OAuth desktop client and gcloud CLI Keep credential files outside your project
Python 3.10 or later, pipx and Git Confirm python3 --version, pipx --version and git --version work
Claude Code Install it and confirm claude --version works
Five-file Skill pack Install the weekly audit; add specialists as needed

Setup time depends on Cloud access, OAuth and your local environment. Production-access approval can add waiting time.

Step 1: How do I enable Cloud access?

Google retired developer tokens on September 9, 2026. Google Ads API access now belongs to your Google Cloud project. Enable the API and check the project's access level before querying production accounts. See Google's migration note.

  1. Select the Cloud project that owns the OAuth client.
  2. Enable the Google Ads API in APIs & Services > Library.
  3. Open the Google Ads API Overview page.
  4. Check whether the project has Test, Explorer, Basic or Standard access.
  5. Apply for production access if the project only has Test access.
  6. Record the project ID for the MCP configuration.

Enabling the API grants Test access. It does not grant production access. Check Google's access-level documentation for current limits and permitted features.

Step 2: How do I set up local OAuth credentials?

  1. Install the gcloud CLI.
  2. Configure the OAuth consent screen in your selected Cloud project.
  3. Add your Google user as a test user if the OAuth app requires it.
  4. Create an OAuth client with the Desktop app type.
  5. Download its JSON file to a private location outside your project.
  6. Replace the placeholder path and run this command:
gcloud auth application-default login \
  --scopes=https://www.googleapis.com/auth/adwords,https://www.googleapis.com/auth/cloud-platform \
  --client-id-file=/ABSOLUTE/PATH/oauth-client.json

Authenticate as the Google user with access to the intended Ads account. Copy the credential path printed after Credentials saved to file:. Use that actual ADC path below. Do not create a new adc.json file.

Keep OAuth and ADC files outside source control. The adwords scope is not a read-only scope. The server's tool configuration controls which audit tools it exposes.

Step 3: How do I disable asset and label tools?

Save this exact configuration as tools_config.yaml in a stable local folder:

namespaces:
  customers: true
  search: true
  metadata: true
  labels: false
  assets: false

Record its absolute path. Pass it explicitly through GOOGLE_ADS_MCP_TOOLS_CONFIG. Do not depend on the working directory to select it.

The reviewed version raises an error if this explicit path does not exist. An empty or unrelated YAML file is not equivalent to this configuration. Without an explicit configuration, the release can load defaults that enable write tools.

Step 4: How do I register the server in Claude Code?

Inspect existing entries first:

claude mcp get google-ads-mcp
claude mcp list

If an entry exists, inspect its scope, launch command and environment paths. Save its settings privately before replacing it. Remove the entry from its actual scope, then register the revised definition. For an existing user entry:

claude mcp remove google-ads-mcp --scope user

Check for the same name in other scopes before adding it again. Claude Code's MCP reference explains scope and configuration conflicts.

Replace the three placeholders below. Quote paths containing spaces. The credential placeholder means the ADC path printed by gcloud.

claude mcp add --transport stdio --scope user google-ads-mcp \
  --env GOOGLE_PROJECT_ID=YOUR_PROJECT_ID \
  --env GOOGLE_APPLICATION_CREDENTIALS=/ABSOLUTE/PATH/adc.json \
  --env GOOGLE_ADS_MCP_TOOLS_CONFIG=/ABSOLUTE/PATH/tools_config.yaml \
  -- pipx run \
  --spec "git+https://github.com/googleads/google-ads-mcp.git@7452a9d49e3d350403f2610cd7125c60f6d05264" \
  google-ads-mcp

For manager-account access, include --env GOOGLE_ADS_LOGIN_CUSTOMER_ID=YOUR_MANAGER_CUSTOMER_ID before -- pipx run. This is the manager ID. Use the separate client customer ID in audit queries.

User and local MCP entries live in ~/.claude.json. Project entries live in project-root .mcp.json. This guide uses user scope. See the MCP quickstart for connection checks. Claude Desktop and Cowork setup are outside this guide.

Run claude mcp get google-ads-mcp and claude mcp list again. Open /mcp inside Claude Code and inspect the server's tools. The reviewed configuration exposes:

  • customers_list_accessible_customers
  • search_search
  • metadata_get_resource_metadata

Asset creation, video upload and label-management tools must be absent. Stop if unexpected write tools appear. Check the revision and configuration before querying account data.

Step 5: How do I verify the connection and reporting period?

  1. Ask Claude to list accessible accounts through the configured server.
  2. Confirm the exact client customer ID.
  3. Retrieve the client's reporting currency and account time zone.
  4. Inspect /mcp for unexpected write tools.
  5. Select an explicit, completed reporting period in the account's time zone.
  6. Query total account spend for those dates.
  7. Compare it with Google Ads for the identical account and dates.
  8. Stop analysis if the totals do not agree.

Accessible accounts can reflect direct access or a manager context. Confirm the intended client rather than assuming a listed manager is the reporting account.

Exclude the in-progress day. Record the start date, end date, currency and time zone. Check cost micros, filters, pagination and account selection when totals differ. Recent conversions can still arrive after a date range ends.

Step 6: How do I install the weekly audit Skill?

  1. Download and extract the five-file pack below.
  2. Extract google-ads-weekly-audit.skill as a ZIP archive.
  3. Place its Skill directory under your personal Claude Code Skills folder.
  4. Confirm ~/.claude/skills/google-ads-weekly-audit/SKILL.md exists.
  5. Keep its references folder beside SKILL.md.
  6. Open Claude Code's / menu and confirm /google-ads-weekly-audit is available.

Personal Skills load from ~/.claude/skills/<skill-name>/SKILL.md, according to the Skills documentation. The same installation steps apply to the other four archives. Check an existing installation before replacing it.

What's running under the hood?

The weekly audit coordinates four base phases. It can use installed specialists or its built-in methods. It records which method ran. Ad-copy review does not require a separate copy-generation Skill.

Phase Method Installation note
Campaign performance ad-performance-diagnostic or the weekly audit's built-in method Included in the pack
Search terms search-terms-analyzer or the weekly audit's built-in method Included in the pack
Negative keywords negative-keyword-miner or the weekly audit's built-in method Included in the pack
Ad-copy review Built into google-ads-weekly-audit A separate copy-generation Skill is optional
PMax review performance-max-auditor Included as an optional add-on

PMax adds a fifth phase when requested. Install performance-max-auditor.skill if you request it. Missing PMax fields limit coverage; the audit cannot promise visibility into all placements or queries.

Step 7: How do I run the audit?

Replace the placeholders in this prompt:

Run google-ads-weekly-audit for customer ID YOUR_CUSTOMER_ID.

Use the configured Google Ads MCP server to retrieve account data.
Use the most recent 28 complete days in the account's reporting time zone.
State the exact start date, end date, currency and time zone before analysis.

My primary conversion is YOUR_CONVERSION_DEFINITION.
My target CPA or ROAS is YOUR_TARGET.
My landing page is YOUR_LANDING_PAGE_URL.

Read and analyze only. Do not create assets, edit labels or apply account changes.

First retrieve total account spend for the selected dates.
Ask me to compare it with Google Ads before continuing.
Stop if the account or totals do not match.

Run the four base audit phases.
Mark missing or unsupported fields as unavailable.
Separate observed spend from estimated savings.
Return evidence and a proposed action for each issue.
Require human review before any negative keywords or budget changes.

If this account runs PMax, also run performance-max-auditor.
Merge its supported checks into the same report.
Skip unsupported PMax checks and explain which data is missing.

The final paragraph explicitly requests the optional PMax phase when relevant. Remove it for a four-phase audit. Prompt restrictions supplement the server configuration. They do not replace it.

What does the report contain?

The report identifies its data source as MCP-based, export-based or mixed. It includes exact dates, currency, time zone and the spend reconciliation. If the connector fails, Claude asks before switching to dated exports.

Depending on available data, it includes campaign metrics, query analysis, negative-keyword candidates, ad-copy drafts and requested PMax checks. Unsupported phases remain incomplete. Its optional health score uses the Skill's stated rubric, not a Google score.

Observed query spend and estimated savings appear separately. Visible search terms may cover less spend than account totals. Zero conversions alone do not justify an exclusion. Low volume, conversion delays and business context need review.

Each proposed action includes evidence, uncertainty and a human owner. The account owner approves and applies changes separately. For related methods, see the Claude Skills library.

Download

Download the 5-skill pack

The download contains search-terms-analyzer.skill, performance-max-auditor.skill, negative-keyword-miner.skill, ad-performance-diagnostic.skill and google-ads-weekly-audit.skill. A separate google-ads-copy-generator.skill is not included or required.

Troubleshooting: what should I check first?

Problem First checks
CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION Confirm production access on the OAuth client's Cloud project
Account permission denied Confirm the authenticated user, client ID and manager-account context
Server absent from Claude Code Check CLI registration, command path, pipx and explicit configuration path
Write tools still visible Stop the audit; check the loaded revision and tool configuration
Spend totals differ Check account, dates, time zone, units, filtering and incomplete retrieval
Skill absent Check the extracted directory and SKILL.md location

How did we check this guide?

We checked the setup against vendor documentation and inspected the packaged files on November 10, 2026. We have not completed a new end-to-end account test of this revision.

We also tested local server startup and tool discovery without customer credentials or account queries. The supplied configuration exposed only the three reporting tools listed above. A missing explicit configuration path caused startup to fail. These checks do not establish account access or report accuracy.

Editorial review: Rananjay Raj approved this BuildWire AI update before publication. Questions or corrections are welcome through our contact page.

Frequently asked questions

Is the Google Ads MCP server official?

Yes. The Google Ads API team publishes it in the googleads GitHub organization and documents it in the developer toolkit.

Can Claude change the account?

This guide disables the server's asset and label write tools. Other configurations can expose those tools. Keep account changes outside this audit workflow.

Do I need to know GAQL?

Claude can construct queries. Review the selected account, dates, fields and totals before trusting the analysis.

How long does setup take?

Setup time depends on Cloud access, OAuth and your local environment. Production-access approval can add waiting time.

What does this replace in my weekly workflow?

It can combine data retrieval and four analysis phases into one report. You still confirm spend, review evidence and approve account changes separately.

Can I run this without the MCP server?

Yes. Use dated campaign, search-term and ad CSV exports after agreeing to the source change. Confirm the account, dates, currency and spend first. The report identifies exports and any missing phases.

Does this work for manager accounts?

Use GOOGLE_ADS_LOGIN_CUSTOMER_ID for the manager context. Specify the separate client customer ID for the audit. The authenticated Google user needs access to that client.

What does it cost?

The MCP server is open source. Claude charges depend on your plan or API usage. Optional hosting can add charges. Google Ads API limits still apply.

What does the report contain?

It reports supported campaign, search-term, negative-keyword and ad-copy checks, with optional requested PMax checks. Missing phases remain incomplete. The health score is the Skill's rubric, not a Google score. Potential savings are estimates, and zero conversions alone do not justify exclusion.

Last reviewed 10 November 2026. Vendor documentation and package checks completed. Rananjay Raj approved this update. A new live account test has not been completed.