google-ads-mcp

Item: google-ads-mcp
Rating: 60
Author: M8ven

MCP server for Google Ads API — 22 tools for campaigns, keywords, RSAs, assets, audiences, geo/device performance, impression share, auction insights, and budget pacing. Community edition with B2B/agency-focused tooling beyond the official Google MCP.

→ ZLeventer/google-ads-mcp-npm · listed on glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings

⚠️

Known vulnerabilities in dependencies: 3 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 3 credentials: GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_REFRESH_TOKEN

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.10.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.10.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.10.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// required environment variables

This server reads these from process.env. You'll be asked to provide them before it can run.

configGOOGLE_ADS_CLIENT_ID— Yes OAuth 2.0 client ID

🔐 secretGOOGLE_ADS_CLIENT_SECRET— Yes OAuth 2.0 client secret

configGOOGLE_ADS_CUSTOMER_ID— Yes Default customer ID (no dashes). Can be overridden per tool call.

🔐 secretGOOGLE_ADS_DEVELOPER_TOKEN— Yes Your Google Ads developer token

configGOOGLE_ADS_LOGIN_CUSTOMER_ID— No Manager account ID for MCC access

🔐 secretGOOGLE_ADS_REFRESH_TOKEN— Yes OAuth 2.0 refresh token

// full audit trail

The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/zleventer-google-ads-mcp-npm-1nzo35)](https://m8ven.ai/mcp/zleventer-google-ads-mcp-npm-1nzo35)

commit: ceaa0dcc2df4b8767ea0268905bd290bb7617f79

code hash: 27da595aedd7a2cdb755eaae7136d1e1ffe64ea0e50e45fc159aba6c612a9c2b

verified: 7/30/2026, 8:14:37 PM

view raw JSON →