Google Ads

What Google Ads MCP server does

The Google Ads MCP server exposes native Google Ads API operations through MCP. It is intended for local use with your own platform credentials, with requests sent directly to Google Ads. The repository provides 35 read tools and 10 write tools that are disabled by default. Write operations require explicit confirmation and show a preview before changes are applied.

Read access covers customer accounts, account hierarchy, account details, campaigns, ad groups, budgets, bidding strategies, conversion actions, recommendations, change events, and health checks. Reporting tools retrieve keyword performance, search terms, landing-page metrics, paid and organic search terms, Shopping data, Performance Max placements and diagnostics, and asset information. Image and video tools return asset metadata and usable image or YouTube-related URLs when supported by the underlying account data.

The Google Ads MCP server also includes Keyword Planner operations for keyword ideas, historical search-volume metrics, and temporary campaign forecasts. This makes it relevant to the 🎯 Marketing category for account analysis, campaign research, and planning workflows.

How it works

An MCP client invokes a tool, and the server translates the request into Google Ads API calls. google_ads_run_gaql accepts raw Google Ads Query Language queries for cases where a dedicated tool is not sufficient. Dedicated reporting tools can plan queries from requested metrics and dimensions, while google_ads_validate_query checks compatibility before execution.

Keyword ideas, historical metrics, and forecasts use Google Ads services outside the GAQL query surface, so they are exposed through dedicated tools rather than raw GAQL. The health-check tool verifies credentials and reports which accessible accounts can be reached without printing secrets.

For manager-account access, the optional login customer ID identifies the MCC used for requests. If it is omitted, the server can discover reachable managers and retain the result for the process lifetime.

Setup and configuration

Version 2.0.1 requires Node.js 22.12 or newer. A source installation uses git clone, npm ci, and npm run build; the MCP client then runs the built dist/cli.js with an absolute path. The README also documents an npx configuration for the published package.

Local setup requires a Google Ads developer token, OAuth client ID, OAuth client secret, and refresh token. The developer token must come from a manager account and needs suitable access for live accounts. The OAuth client is created in a Google Cloud project with the Google Ads API enabled. A refresh token is obtained through the OAuth consent flow and should be protected as a secret.

Set GOOGLE_ADS_LOGIN_CUSTOMER_ID when querying accounts under a manager account. After configuration, run google_ads_health_check before other requests to identify missing credentials or inaccessible accounts.

Tools and capabilities

• List accessible accounts and manager/client relationships.
• Inspect campaigns, ad groups, budgets, bids, conversions, recommendations, and account changes.
• Query performance by keyword, search term, landing page, Shopping product, or Performance Max placement.
• List image, video, Demand Gen, and Performance Max asset information.
• Validate and execute GAQL queries.
• Generate keyword ideas, historical metrics, and forecast metrics.
• Prepare supported account changes through opt-in, preview-first write tools.