The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Vibeads MCP listing page.
Talk to your Google Ads account from Claude Desktop, Cursor, or any MCP client.
Built for local service businesses — 33 categories with tuned keywords, CPC benchmarks and funnel templates.
The official Model Context Protocol server for VibeAds. Ask Claude questions like "which search terms are wasting my budget?" or "what's my account health score?" and get answers pulled from your live campaign data.
Unlike generic Google Ads MCP servers, this one is pre-tuned for local service businesses and rolls up 35+ diagnostic rules into a single 0-100 account health score across 6 dimensions. On Pro/Max plans it can also draft campaign strategies, execute guarded optimizations, and kick off publish flows — with a human always approving anything that spends money.
Local & home services (25): plumber · HVAC · electrician · roofer · cleaner · landscaper · pest control · painter · handyman · locksmith · garage door · appliance repair · tree service · fencing · windows & doors · carpet & flooring · waterproofing · pressure washing · pool services · junk removal · movers · auto repair · Christmas lighting · dentist · lawyer
Professional & lead-gen (8): real estate · insurance · financial services · education · healthcare · consulting · SaaS · B2B services
Any other category is accepted — it just falls back to generic defaults instead of the tuned knowledge base.
Sign in to your VibeAds account and generate an API key:
Keys start with vba_mcp_ and are scoped to your account only.
Open your config file:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Add this to the mcpServers block:
Restart Claude Desktop. You should see the VibeAds tools appear in the 🔨 tool menu.
vibeadsnpx -y @vibeads/mcpVIBEADS_API_KEY=vba_mcp_YOUR_KEY_HEREUse the same config as Claude Desktop above. Most MCP clients follow the same schema.
Setup is one env var — every tool (read and write) runs through the secure server-side VibeAds gateway with your API key.
| Variable | Required? | Purpose |
|---|---|---|
VIBEADS_API_KEY | ✅ Required | Your vba_mcp_... key. This is the only credential any tool needs. |
VIBEADS_SUPABASE_URL | Optional | Override the VibeAds backend URL. Defaults to the production endpoint. |
Once configured, you can ask Claude questions like:
"Show me all my VibeAds campaigns"
"Which campaigns are paused?"
"Give me the 5 most recently created campaigns"
"Tell me everything about my plumber campaign in Austin"
"How did my HVAC campaign perform last week?"
"What's the CPA for campaign abc12345?"
"What's my VibeAds account health score?"
"Which dimension is pulling my score down?"
"Give me the health score just for campaign xyz"
"What search terms are wasting my budget?"
"Show me the top 10 winning keywords from the last 30 days"
"How much am I wasting on terms with zero conversions?"
"What should I fix first?"
"Show me all critical diagnostics"
"What's wrong with my roofing campaign?"
| Tool | Purpose |
|---|---|
list_campaigns | Enumerate all campaigns with status, budget, category |
get_campaign_details | Deep dive on one campaign: metrics, ad groups, targeting, landing pages, diagnostics |
get_account_health_score | 0-100 score + letter grade across 6 dimensions, optionally per-campaign |
get_search_term_analysis | Wasted spend + winners from search terms report (configurable lookback + threshold) |
get_diagnostics | Full list of active agent-optimize diagnostics with severity + recommended fix |
The read tools are read-only — they cannot create, modify, pause, or delete anything in your Google Ads account. They run server-side through the VibeAds gateway and need only VIBEADS_API_KEY. Read tools work on any plan, free tier included.
Write tools talk to the secure server-side VibeAds gateway and need only VIBEADS_API_KEY — no Supabase keys. Every action runs inside VibeAds' safety guardrails (blast-radius caps, rate limits, auto-rollback if metrics worsen), and publishing always requires a human approving in the browser — the API key alone can never spend money.
| Tool | Purpose |
|---|---|
generate_strategy | Draft a full campaign strategy (keywords, ad copy, 3+ ad groups) server-side. Costs 13 credits. Draft only — nothing is published, no money is spent |
get_strategy_status | Poll a strategy job: status, phase, and drafted ad groups once complete |
apply_strategy | Turn a completed preview into a real draft campaign (ad groups, keywords, targeting, ad copy, extensions). Costs 6 credits + 3 per ad group for image generation. Draft only — not live, no ad money spent |
list_recommendations | Pending optimization recommendations awaiting approval, with the session + recommendation IDs |
approve_recommendation | Execute ONE diagnosed optimization inside the safety guardrails; sibling recommendations stay pending |
request_publish | Start the publish flow for a campaign that has ad groups — returns a human-approval URL because publishing spends real money |
check_approval | Poll a publish approval: pending → approved → executing → executed (or rejected / expired / failed) |
From idea to live campaign:
generate_strategy drafts the strategy server-side and returns a jobId. Nothing exists in Google Ads yet.get_strategy_status polls that job until it reports completed.apply_strategy turns the finished preview into a real draft campaign and returns a campaignId. Still not live, still spending nothing.request_publish takes that campaignId and returns an approval link.check_approval polls until the campaign is live.Steps 1–3 create rows only in VibeAds and spend VibeAds credits (13 for step 1; 6 + 3 per ad group for step 3). Step 5 is the only point where ad money is committed, and it can only happen in a browser — the API key alone can never publish.
https://getvibeads.com/app/settings/mcp.For maximum security, rotate your API key whenever a device changes hands or an engagement ends.
npx runtime)| VibeAds MCP | GoMarble MCP | Google Ads MCP (official) | |
|---|---|---|---|
| Setup time | 2 min | 15 min | 30 min |
| OAuth required | ❌ (API key only) | ✅ | ✅ |
| GAQL knowledge required | ❌ | ✅ | ✅ |
| Local service tuning | ✅ | ❌ | ❌ |
| Account health score | ✅ 6 dimensions | ❌ | ❌ |
| Pre-built diagnostics | ✅ 35+ rules | ❌ | ❌ |
| Multi-account | ✅ | ✅ | ✅ |
| Guarded write actions | ✅ human-approved publish | ❌ | ❌ |
When to use VibeAds MCP: You run a local service business (or manage ads for one) and want pre-tuned insights without learning GAQL.
When to use GoMarble / Google Ads MCP: You need to run custom GAQL queries or work with non-service-business campaigns (e-commerce, B2B SaaS, etc.).
The three can coexist — install whichever ones fit your workflow.
vba_mcp_Diagnostics are generated every 6 hours by the VibeAds agent. If you just published a campaign, wait 6-12 hours for the first run.
Search term sync runs every 6 hours. For new campaigns, allow 24-48 hours for meaningful data to accumulate.
Make sure you have Node.js 20+ installed: node --version. Claude Desktop and Cursor both shell out to npx, so Node must be in your PATH.
This is an open-source MIT package. Issues and PRs welcome at: https://github.com/vibeads/mcp/issues
MIT © VibeAds