MCP Tools Directory
← Browse integrations

Developer tools

io.github.mharnett/google-ads

Free account · sign-in required

Contact io.github.mharnett/google-ads

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

Google Ads MCP with MCC support: 35 tools for campaigns, keywords, reporting, GAQL.

Transport
stdio
Authentication
oauth
Initial setup
user-authorization
Runtime
unattended
Evidence
documented
Version
1.0.1
Package
mcp-google-ads
Last compatibility test
Not independently tested

Connect your agent

mcp-google-ads

Publisher documentation and package manifest were reviewed offline. The package was not installed or executed, Google Ads was not contacted, credentials were not used, and runtime/security behavior was not independently verified. A Google Ads developer token and OAuth client credentials plus refresh token are required. The documented server is read-only by default; mutating tools require GOOGLE_ADS_MCP_WRITE=true, and publisher-described pause/approval safeguards still require operator review.

Capabilities: List Google Ads campaigns, ad groups, conversions, and pending changes, Query Google Ads performance, search-term, keyword-volume, and GAQL reports, Create and manage campaigns, ads, assets, keywords, and tracking when writes are explicitly enabled

Connected profiles

Additional details

Registry identifier

io.github.mharnett/google-ads

Source ↗ · Checked 2026-09-17
Published version

1.0.1

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Required configuration names

GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_REFRESH_TOKEN, GOOGLE_ADS_DEVELOPER_TOKEN

Source ↗ · Checked 2026-09-17
Source artifact

mcp-google-ads

Source ↗ · Checked 2026-09-19
Source manifest version

1.11.0

Source ↗ · Checked 2026-09-19
Unattended configuration

Node.js 18.18 or newer runs the documented stdio MCP process. Once OAuth and Google Ads credentials are provisioned, the server reads configuration on each request and exposes read-only tools unless the separate write flag is enabled.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

Requires a Google Ads developer token, OAuth client ID and secret, and a refresh token minted through the documented interactive Google authorization flow; the server then uses the provisioned credentials at runtime.

Source ↗ · Checked 2026-09-19
Connection configuration

Configure the MCP client to launch node with node_modules/mcp-google-ads/dist/index.js over stdio; a source install may instead use an absolute dist/index.js path.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19