Generic Google Ads servers hand back rows and leave the reading to you; this one carries rules written for local trades and orders them by severity. The write side is built the same way — an optimization runs inside guardrails, and a publish comes back as a link you have to open and approve.
VibeAds' own MCP server over a Google Ads account, tuned for local service trades — plumbers, HVAC, electricians, roofers and 33 more categories. Read tools answer in markdown with no GAQL to write; write tools draft strategies and run optimizations through the VibeAds gateway, and anything that spends money waits for a human in the browser.
- Campaigns listed with status, budget and category, and one campaign opened out in full — metrics, ad groups, targeting, landing pages, diagnostics
- A 0-100 account health score with a letter grade, weighted across tracking, keywords, budget, creative, targeting and performance, whole-account or per campaign
- Search-term analysis over a lookback window you set: the spend going to terms that never convert, and the winners
- 35+ diagnostic rules from the optimization engine, each with severity and a recommended fix, so the worst problem reads first
- A full campaign strategy drafted server-side — keywords, ad copy, three or more ad groups — as a draft that publishes nothing, and a poll for the job while it runs
- Pending recommendations listed and executed one at a time inside blast-radius caps, rate limits and automatic rollback if metrics worsen
- A publish flow that returns a browser approval link, and a poll that follows it from pending through approved to executed
Node.js 20 or newer and a VibeAds account. One credential does everything: VIBEADS_API_KEY, a vba_mcp_ key generated in settings and scoped to your account. Read tools work on any plan including the free tier; the write tools need Pro or Max. Runs over stdio from npm as @vibeads/mcp.
One command plus a key — npx -y @vibeads/mcp, then supply credentials