Google Ads MCP server. Read campaigns, manage budgets, pause/enable, add negative keywords.
The AI layer between your Google Ads account and your marketing decisions. Battle-tested. Six tools cover the daily-ops loop — campaign listing, search-term review, budget tuning, pause/enable, and negative-keyword grooming. All responses are strict Pydantic models. No raw protobuf reaches the agent. The open-source server runs locally with your own API keys. For hosted infrastructure with…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
The AI layer between your Google Ads account and your marketing decisions. Battle-tested. Six tools cover the daily-ops loop — campaign listing, search-term review, budget tuning, pause/enable, and negative-keyword grooming. All responses are strict Pydantic models. No raw protobuf reaches the agent. The open-source server runs locally with your own API keys. For hosted infrastructure with multi-account failover, SLA guarantees, and webhook alerts — join the managed cloud waitlist. Raw Google…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.