About this integration
Unofficial MCP server for Google Ads: reporting plus safe draft/confirm campaign management.
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.0.0
- Package
- google-ads-manager-mcp
- Last compatibility test
- Not independently tested
Connect your agent
google-ads-manager-mcpPublisher documentation and executable manifest reviewed from pinned captures; package and provider endpoints were not executed or independently security-audited. After one browser OAuth authorization, the configured refresh token and developer credentials support later local MCP calls without another interactive step.
Capabilities: Query Google Ads reporting data, Draft campaign and budget changes, Confirm guarded Google Ads writes, Manage keywords, ad groups, and ads
Connected profiles
Additional details
io.github.AleemHaider/google-ads-manager-mcp
Source ↗ · Checked 2026-09-171.0.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_REFRESH_TOKEN, GOOGLE_ADS_CUSTOMER_ID
Source ↗ · Checked 2026-09-17google-ads-manager-mcp
Source ↗ · Checked 2026-09-181.0.0
Source ↗ · Checked 2026-09-18After one browser OAuth authorization, the configured refresh token and developer credentials support later local MCP calls without another interactive step.
Source ↗ · Checked 2026-09-18Setup requires a Google Ads developer token, OAuth desktop client credentials, and a refresh token obtained by authorizing the adwords scope.
Source ↗ · Checked 2026-09-18Launch the built Node entrypoint from the MCP client with the documented Google Ads credential environment.
Source ↗ · Checked 2026-09-18Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-18