google-ads-api-mcp-setup
Guides developers through downloading, configuring, and installing the official open-source Google Ads MCP Server. Use this skill when a user wants to connect their AI assistant (such as Gemini, Claude Code, or Cursor) to their Google Ads account to query campaigns or retrieve reporting metrics using natural language.
Security Assessment
About google-ads-api-mcp-setup
The google-ads-api-mcp-setup skill is a structured installation and configuration guide for the official open-source Google Ads Model Context Protocol (MCP) Server. It solves the setup friction of connecting an AI assistant (such as Gemini, Claude Code, or Cursor) to a Google Ads account so users can query campaigns and retrieve reporting metrics in natural language. Rather than shipping code, it directs the agent through a repeatable, safety-checked installation flow that points only at the official package and repository.
The skill lays out prerequisites (Python 3.12+ and pipx, plus outbound HTTPS to the Google Ads API and PyPI) and a credential checklist covering the five standard Google Ads API parameters: Developer Token, OAuth2 Client ID and Client Secret, OAuth2 Refresh Token, and Customer IDs, with formatting rules (digits only, no hyphens) and a login Customer ID for MCC hierarchies. If credentials are missing it defers to a companion quickstart skill. It then walks through verifying and installing prerequisites with OS-specific commands (Homebrew, scoop, or apt, plus pipx ensurepath), installing the stable google-ads-mcp package from PyPI by default (GitHub development version only on explicit request), verifying with a --help command, troubleshooting PATH issues via the pipx bin directory, and explaining the stdio transport for the MCP connection.
It targets developers and marketing engineers who want to wire an AI assistant to Google Ads reporting. The credential handling follows standard official-tooling practice: it documents the required tokens and OAuth values but does not exfiltrate them, and it explicitly steers users to the vetted official server rather than third-party ones.
FAQ
What do I need before installing?
Python 3.12+ and pipx installed and on PATH, outbound HTTPS access to the Google Ads API and PyPI, and the five Google Ads API credentials (Developer Token, OAuth2 Client ID/Secret, Refresh Token, and Customer IDs).
How is the server installed?
By default via pipx from PyPI (pipx install google-ads-mcp). The GitHub development version is only installed if the user explicitly requests it. Installation is verified with google-ads-mcp --help.
What if I don't have my credentials yet?
The skill instructs stopping and switching to the companion google-ads-api-quickstart skill to generate the Developer Token, Client ID/Secret, Refresh Token, and Customer IDs, then returning.
How does the assistant communicate with the server?
Over stdio transport, which the skill requires the agent to explain as part of a mandatory setup checklist along with stating prerequisites and using the official install command.
Install google-ads-api-mcp-setup
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
google/skills