OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Google Ads MCP

Google Ads MCP is a Python Model Context Protocol server that connects compatible AI clients to the Google Ads API, exposing account, campaign, ad and query tools for conversational advertising analysis and management.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Google Ads MCP — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when an MCP-compatible AI client is part of the workflow and you want natural-language access to Google Ads reporting, performance analysis or account operations.

Who it is for

  • Advertising professionals who want to ask an AI client about Google Ads campaign and account data.
  • Teams or developers configuring an MCP server with Claude Desktop, Cursor or another compatible client.
  • Users who need to retrieve campaign, ad or keyword metrics through predefined tools or GAQL queries.

Documented uses

  • List Google Ads accounts and retrieve basic account and campaign information.
  • Compare campaign performance, trends and time periods using impressions, clicks, conversions and cost metrics.
  • Review keyword and ad performance, including quality scores and competitive metrics.
  • Monitor budget and bid performance and obtain optimization or budget-allocation recommendations.
  • Run a custom GAQL query and return formatted results.
Before you choose

Requirements & limits

The repository is public and MIT-licensed. Use requires Google Ads API credentials and a developer token; documented authentication options are OAuth 2.0 and service account credentials.

  • It is an MCP server that must be configured with a compatible client, rather than a standalone reporting interface.
  • The README documents Claude Desktop and Cursor configuration and describes connecting other AI clients.
  • Predefined tools cover account lists and campaign or ad performance; GAQL tools support custom queries.
  • Authentication, account permissions, developer-token access level and API quotas affect what can be retrieved.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Configure Google Ads API credentials for an MCP client

Prepare credentials and environment configuration for the Google Ads MCP server.

Before you start

  • A Google Cloud project with the Google Ads API enabled.
  • A Google Ads API developer token.
  • Either an OAuth 2.0 client configuration or a service-account key; service accounts must be granted access to the Google Ads account.
  • The repository's .env.example file, or an MCP client configuration file.

Steps

  1. Create the selected OAuth client ID or service account credentials in Google Cloud Console and save the credentials file.

  2. Copy .env.example to .env and set GOOGLE_ADS_AUTH_TYPE, GOOGLE_ADS_CREDENTIALS_PATH and GOOGLE_ADS_DEVELOPER_TOKEN; set GOOGLE_ADS_LOGIN_CUSTOMER_ID if applicable.

  3. Alternatively, add the documented server command, script path and environment values to the MCP configuration for Claude Desktop or Cursor.

Expected outcome

The server has the documented credentials and configuration values needed for an MCP client connection.

Guide limitations

  • The guide covers configuration, not successful connection or deployment.
  • Google Ads account permissions, developer-token access level and API quotas can affect access.
  • The README's configuration examples require replacing placeholder paths and values.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
cohnen/mcp-google-ads · Official homepage title · retained in its source language
How we review sourcesSuggest a correction