MCP server acting as an interface to the Google Ads, enabling programmatic access to Google Ads data and management features.
Most cloud and infrastructure work still happens through a UI a human drives. Google Ads MCP server moves it into the conversation instead. MCP server acting as an interface to the Google Ads, enabling programmatic access to Google Ads data and management features.
Connect Google Ads API directly to Claude Desktop and other MCP clients with seamless OAuth 2.0 authentication, automatic token refresh, GAQL querying, and keyword research capabilities.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 5 tools. What each one is for:
list_accounts — List all accessible Google Ads accountsrun_gaql — Execute GAQL queries with custom formattingrun_keyword_planner — Generate keyword ideas with metricsIssue — SymptomsPrerequisites — Before setting up the MCP server, you'll need: - Python 3.10+ installed - A Google Cloud Platform account - A Google Ads account with API accessConfiguration is passed through the environment: GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_OAUTH_CONFIG_PATH, GOOGLE_ADS_LOGIN_CUSTOMER_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before setting up the MCP server, you'll need: - Python 3.10+ installed - A Google Cloud Platform account - A Google Ads account with API access
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google Ads's toolset — list_accounts, run_gaql, run_keyword_planner and 2 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list_accounts | List all accessible Google Ads accounts |
| run_gaql | Execute GAQL queries with custom formatting |
| run_keyword_planner | Generate keyword ideas with metrics |
| Issue | Symptoms |
| Prerequisites | Before setting up the MCP server, you'll need: - Python 3.10+ installed - A Google Cloud Platform account - A Google Ads account with API access |
{
"mcpServers": {
"google-ads": {
"command": "/full/path/to/your/project/.venv/bin/python",
"args": [
"/full/path/to/your/project/server.py"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Before setting up the MCP server, you'll need: - Python 3.10+ installed - A Google Cloud Platform account - A Google Ads account with API access
| Variable | Description | Required |
|---|---|---|
| GOOGLE_ADS_DEVELOPER_TOKEN | Credential the server authenticates with. | Yes |
| GOOGLE_ADS_OAUTH_CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.