MCP Google Ads logo

MCP Google Ads

Claimed

by cohnen

An MCP tool that connects Google Ads with Claude AI/Cursor and others, allowing you to analyze your advertising data through natural language conversations. This integration gives you access to campaign information, performance metrics, keyword analytics, and ad management—all through simple chat with Claude, Cursor or Windsurf.

Install

$pip install uv

Set up this server

Compare serversMy Stack

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
aiclaudegoogle-adsmcpmcp-server

More in Communication

Browse the full directory

Badge

Show this listing on your README and website

Get verified and your listing links back to your site with a do-follow link. The badge is optional while first-100 launch spots remain.

MCPVault: claimedGet the embed code

Security profile

Exposure: Limited

Runs commands or loads code on your machine, but does not reach secrets or other agents.

What this server can reach, from a static read of the shipped code. Nothing was executed and nothing here is a verdict: a browser tool has to run commands and an API wrapper has to call its API. Decide what fits your setup.

NVIDIA SkillSpector v2.11.0, MCPVault MCP-server policy. Scanned yesterday @ 461a1d6.

Detected

  • Talks to external services2 places

    Makes outbound requests. The hosts are listed so you can see where data goes.

    api.surgemsg.com, api.weather.com

  • Runs shell commands2 places

    Spawns processes on your machine. Expected for command, browser and build tools.

  • Reads local configuration files3 places

    Loads a .env, .npmrc or config file. Normal for a server that needs an API key.

  • Contains instructions aimed at AI agents5 places

    Text in code or agent-facing files that steers a model. Worth reading before you trust it.

  • Runs unpinned packages at runtime6 places

    Executes npx or uvx without a version, so a compromised upstream release would run.

Not detected: reads environment variables in bulk, sends conversation content outward, reads or writes other agents' configuration, accesses credential files, uses elevated privileges, installs itself to run later, matches a known malicious pattern.

Dependencies with known advisories

None found in the lockfiles and manifests checked against OSV.dev.

Left out of the profile

47 pattern matches in documentation, configuration or CI files were recorded but are not part of the profile, because they do not run when the server does. The owner dashboard lists them.

How the profile works Maintainers see file, line and a fix for each item in their dashboard.

Documented tools (5)

From project documentation. A server handshake does not verify each tool’s description or behavior.

execute_gaql_query

Runs a Google Ads Query Language query

get_ad_performance

Detailed analysis of your ad creative performance

get_campaign_performance

Shows campaign metrics with performance data

list_accounts

Shows all your Google Ads accounts

run_gaql

Runs any arbitrary GAQL query with formatting options

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about MCP Google Ads MCP Server

How do I connect MCP Google Ads MCP Server to Claude?
The listing records `pip install uv` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Cursor as compatible clients.
Is MCP Google Ads MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can MCP Google Ads MCP Server do?
MCP Google Ads MCP Server documents 5 tools to the agent, including execute_gaql_query, get_ad_performance, get_campaign_performance. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.