Overview
What is Mcp Google Ads?
Mcp Google Ads is a multi-account Google Ads MCP server that connects any number of Google Ads accounts to MCP-compatible AI assistants like Claude, Cursor, or Codex. It allows users to query campaign performance, keywords, search terms, and account analytics by account name in the same session.
How to use Mcp Google Ads?
Install via uvx mcp-google-ads-multi, then create a JSON configuration file for your accounts with OAuth or service account credentials. Set the GOOGLE_ADS_DEVELOPER_TOKEN environment variable and point GOOGLE_ADS_ACCOUNTS_CONFIG to your config file. Add the server to your MCP client’s configuration (e.g., claude_desktop_config.json) and restart the client. Once set up, you can ask natural‑language questions about your accounts.
Key features of Mcp Google Ads
- Supports multiple named Google Ads accounts, switchable per tool call.
- Mixed authentication: OAuth and service account per account.
- Provides quality score data for keywords.
- Includes search terms report (actual user queries).
- Automatic rate‑limit retry with exponential backoff.
- Supports SSE transport for remote deployment.
Use cases of Mcp Google Ads
- Query campaign performance for a specific account over a date range.
- Compare spend or conversions between two time periods side by side.
- Identify keywords with low quality scores to optimize bidding.
- Retrieve the actual search queries that triggered conversions.
- List all accessible Google Ads customer accounts under a login.
FAQ from Mcp Google Ads
How many Google Ads accounts can I configure?
The README shows any number of accounts can be defined in the configuration file, and they can be switched by name per tool call without restarting the server.
What authentication methods are supported?
Both OAuth (desktop client) and service account authentication are supported, and they can be mixed per account in the same configuration.
Do I need a developer token?
Yes, a Google Ads API developer token is required. It is free and can be obtained from the Google Ads API Center (processing takes about 3 business days).
What transport options are available?
The default transport is stdio. Setting MCP_TRANSPORT to sse enables remote deployment, with configurable bind host and port.
Does the server include quality score and search term data?
Yes. The server provides keyword quality scores and a search terms report (actual user search queries that triggered your ads), features not commonly found in other Google Ads MCP servers.
