Last updated: 16 November 2026. Google Ads API (v26.2), Anthropic and OpenAI documentation checked that day.
Yes, there is an official way. Google publishes an open-source Google Ads MCP server (googleads/google-ads-mcp) with a developer integration guide in the Google Ads API docs (Google’s guide). You run it yourself, locally over stdio or remotely on Cloud Run, and point Claude at it. This walkthrough covers the local Claude Code route; for Claude.ai on the web see Connect Claude.ai to Google Ads with a remote MCP server on Cloud Run.
The six steps
| Step | What you do | Time |
|---|---|---|
| 1 | Create/select a Google Cloud project and enable the Google Ads API (Test access) | 5 min |
| 2 | Apply for Explorer access on the Google Ads API Overview page | Minutes, usually automated |
| 3 | Create an OAuth client (Desktop app) and run gcloud ADC login with the adwords scope | 10 min |
| 4 | Install Python 3.10+ and pipx; add the server with claude mcp add | 5 min |
| 5 | Set permission rules (and optionally read-only tools_config.yaml) | 5 min |
| 6 | Ask Claude to list accessible customers | 1 min |

Step 1–2: Cloud project and access level
Developer tokens were sunset on 9 September 2026. Access is now granted per Google Cloud project: enabling the API gives Test access (test accounts only, 15,000 operations a day), and you apply for Explorer on the Google Ads API Overview page in Cloud Console to reach production accounts (up to 2,880 operations a day, approved automatically in most cases) (sunset FAQ, access levels). The project that owns your OAuth client decides your level.
Step 3: credentials
# 1) Google Cloud project: enable the Google Ads API (grants Test access),
# then apply for Explorer access on the "Google Ads API Overview" page.
# 2) Local ADC with the adwords scope (OAuth client JSON from the same project)
gcloud auth application-default login \
--scopes https://www.googleapis.com/auth/adwords,https://www.googleapis.com/auth/cloud-platform \
--client-id-file=client_secret.jsonAlternatively use a service account by pointing GOOGLE_APPLICATION_CREDENTIALS at its key, or impersonate one with gcloud. Keep key files out of repos and never paste them into a chat.
Step 4: add the server to Claude Code
# Claude Code: add Google's open-source Google Ads MCP server (local stdio)
claude mcp add --transport stdio --scope project \
--env GOOGLE_CLOUD_PROJECT=my-gcp-project \
--env GOOGLE_ADS_LOGIN_CUSTOMER_ID=1234567890 \
google-ads -- pipx run --spec google-ads-mcp==0.0.6 google-ads-mcp
claude mcp listEverything after -- is the command that starts the server; --scope project writes a shared .mcp.json (Claude Code MCP docs). For Claude Desktop or other hosts, Google’s guide gives this JSON block for the MCP config file:
{
"mcpServers": {
"google-ads-mcp": {
"command": "pipx",
"args": ["run", "--spec", "google-ads-mcp==0.0.6", "google-ads-mcp"],
"env": {
"GOOGLE_CLOUD_PROJECT": "PROJECT_ID",
"GOOGLE_APPLICATION_CREDENTIALS": "PATH_TO_CREDENTIALS_JSON"
}
}
}
}If you reach client accounts through a manager account, set GOOGLE_ADS_LOGIN_CUSTOMER_ID (10 digits, no hyphens) or pass login_customer_id per call.
Step 5: permissions
// .claude/settings.json - reads allowed, asset/label writes always asked
{
"permissions": {
"allow": [
"mcp__google-ads__customers_list_accessible_customers",
"mcp__google-ads__search_search",
"mcp__google-ads__metadata_get_resource_metadata"
],
"ask": [
"mcp__google-ads__assets_create_asset",
"mcp__google-ads__labels_manage_labels",
"mcp__google-ads__labels_manage_label_associations"
],
"deny": [
"mcp__google-ads__assets_upload_video_asset"
]
}
}For analysts who should only read, also switch write namespaces off on the server:
# tools_config.yaml - strictly read-only deployment
# (point GOOGLE_ADS_MCP_TOOLS_CONFIG at this file)
namespaces:
customers: true
search: true
metadata: true
labels: false
assets: falseStep 6: first prompts
| Prompt | Tool Claude uses | Read or write |
|---|---|---|
| “What customers do I have access to?” | customers_list_accessible_customers | Read |
| “How many active campaigns do I have?” | search_search | Read |
| “Which fields can I filter on for ad_group?” | metadata_get_resource_metadata | Read |
| “Create a callout asset: Free UK returns” | assets_create_asset (propose, then confirm) | Write |
| “Label campaign X as q4-test” | labels_manage_labels / associations | Write |

Read tools query the API directly. Write tools first run with validate_only=True, return change_items and a checksum, and commit only after you approve. Note the boundaries: the server cannot change campaigns, ad groups, ads, budgets or bids, and cannot link assets to campaigns. Guardrail patterns are in Claude Code guardrails for Google Ads: read-only mode and approvals; reporting recipes in Claude GAQL reporting (Chinese).
Optional: Google’s agent skills
Google also ships agent skills for Claude Code, Codex, Cursor and Antigravity, including an MCP setup skill and an account diagnostics skill (agent skills):
# Google's agent skills for Google Ads (works with Claude Code, Codex, Cursor, Antigravity)
npx skills add google/skills/skills/ads
# includes e.g. google-ads-api-mcp-setup, google-ads-api-account-diagnostics,
# google-ads-api-quickstartIf it fails
CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION: apply for Explorer for the project that owns your OAuth client.- Permission denied on a client account: set the login customer ID to the manager account.
- Tools missing from your allow rules: names are prefixed since v0.0.6 (e.g.
search_search). - Server slow to start:
pipx install google-ads-mcponce, then usegoogle-ads-mcpas the command.
How PandaWM uses Claude, Codex and Google Ads accounts to speed up client ad delivery
This guide focuses on Claude, but in day-to-day client work PandaWM combines Claude, Codex and Google Ads accounts to help companies going global move faster through the repetitive loop of account and conversion setup → campaign builds → ad copy and assets → reports and search terms → budget and negative-keyword changes, so media buyers spend their time on strategy, bidding judgement and creative.
- Ad accounts: the client’s own Google Ads account, or one opened compliantly through PandaWM’s account-opening service. The account belongs to the client and is never rented or shared; multi-account access goes through the client’s own manager account.
- Claude: natural-language reporting (GAQL) through Google’s open-source Google Ads MCP server, impression-share and search-term diagnosis, RSA headline/description and asset drafts, and asset or label creation in propose-and-confirm mode.
- Codex: writing and maintaining google-ads Python scripts (daily reports, search-term clean-up, paused campaign builds, validate_only pre-checks) that run in a sandbox, on a schedule or in CI.
- Human sign-off: a media buyer approves enabling campaigns, budget increases and bid-strategy changes, and a person makes the final call on Google Ads policy and landing-page compliance.
This describes a service capability only. There are no prices or rebates here, and PandaWM is not an official partner of Google, Anthropic or OpenAI. See Google Ads account opening & management (PandaWM service page) for account opening and management.
FAQ
Is the Google Ads MCP server hosted by Google?
No. It is Google’s open-source project that you run yourself; community support is via GitHub issues and the #ads-api-ai-tools channel on Discord.
Do I need a manager (MCC) account?
No. Since the developer token sunset you can start without one. Use your own manager account only if you manage several accounts.
Which Claude plan do I need?
Claude Code works with Anthropic accounts in supported regions; remote custom connectors on Claude.ai vary by plan. Check supported regions.
Can Claude spend money through this?
Not directly: there are no campaign, budget or bid tools. Asset creation needs your confirmation.
Compliance note: Use every workflow in this guide only on Google Ads accounts (including client accounts under a manager account) that your company owns or is formally authorised to manage, through Google’s official Google Ads API, Google’s open-source Google Ads MCP server or official tools such as Google Ads Editor. Follow the Google Ads API Terms and Conditions, API quotas and Google Ads policies, and keep a human review step before anything that can spend money. PandaWM does not sell, rent, share or transfer ad accounts, manager accounts or API credentials, does not help anyone bypass ad review, regional restrictions, identity verification or payment controls, and is not an official partner of Google, Anthropic or OpenAI. Claude and OpenAI services are only offered in their supported countries and regions; the account holder should be an entity legitimately established and operating in a supported region.
Related guides
- Google Ads account opening & management (PandaWM service page)
- Overseas AI Token service: account setup + API access (PandaWM)
- Connect Claude.ai to Google Ads with a remote MCP server on Cloud Run
- Claude for Google Ads RSA and Performance Max asset creation
- Claude Code guardrails for Google Ads: read-only mode and approvals
- Codex config.toml for the Google Ads MCP server
- Google Ads MCP server: let AI agents work on your ads
- How to connect Claude to Facebook Ads (step by step)
- How to get a Claude (Anthropic) API key
Talk to PandaWM: Google Ads accounts + AI-assisted delivery
Tell us where your company is registered, your industry, target countries, landing page and expected monthly budget, and which part you want to automate first (reporting, search terms, assets or campaign builds). We pre-check eligibility and landing pages, help you open your own Google Ads account compliantly, and wire Claude / Codex into your workflow.
WhatsApp: +852 5904 8602Telegram: @PANDA0134WeChat: szcwh99

Official sources
- Google: Google Ads MCP server – developer integration guide
- GitHub: googleads/google-ads-mcp
- Google: Developer token sunset (2026-09-09) and FAQ
- Google: Google Ads API access levels
- Google: Google Ads API AI agent skills
- Anthropic: Connect Claude Code to tools via MCP
- Anthropic: Claude Code permissions
- Anthropic: Supported regions
All official pages checked on 2026-11-16. API versions, tool names and permission requirements change; the official pages prevail.

微信扫一扫打赏
支付宝扫一扫打赏
