Odel
mcp

mcp

Local
@vibeadsTypeScriptMITUpdated 2 days ago

Manage Google Ads from Claude: read metrics, draft campaigns, publish with human approval.

@vibeads/mcp

npm version License: MIT MCP

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.


Features

  • ๐ŸŽฏ Local-service-first โ€” 25 home-service verticals plus 8 professional/lead-gen ones, each with its own keyword seeds, CPC benchmarks, audience segments and funnel template
  • ๐Ÿ“Š Account Health Score 0-100 โ€” weighted across 6 dimensions (Tracking, Keywords, Budget, Creative, Targeting, Performance)
  • ๐Ÿ” Search term waste detection โ€” finds every dollar burning on zero-conversion terms
  • ๐Ÿ’ก Diagnostic rollup โ€” 35+ rules from VibeAds' optimization engine, ranked by severity
  • โœ๏ธ Write tools (Pro/Max) โ€” draft strategies, approve optimizations, and start publish flows through the VibeAds gateway
  • ๐Ÿ”’ Safe by design โ€” read tools can't modify anything; write tools run inside VibeAds' safety guardrails, and publishing always requires a human to approve in the browser
  • โšก No GAQL required โ€” ask questions in natural language, get markdown answers

Supported categories

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.


Installation

Step 1 โ€” Get your API key

Sign in to your VibeAds account and generate an API key:

โ†’ Generate API key

Keys start with vba_mcp_ and are scoped to your account only.

Step 2 โ€” Configure your MCP client

Claude Desktop

Open your config file:

OSPath
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:

{
  "mcpServers": {
    "vibeads": {
      "command": "npx",
      "args": ["-y", "@vibeads/mcp"],
      "env": {
        "VIBEADS_API_KEY": "vba_mcp_YOUR_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop. You should see the VibeAds tools appear in the ๐Ÿ”จ tool menu.

Cursor

  1. Open Settings โ†’ MCP
  2. Click Add Server
  3. Configure:
    • Name: vibeads
    • Command: npx -y @vibeads/mcp
    • Environment variables: VIBEADS_API_KEY=vba_mcp_YOUR_KEY_HERE

Cline / Claude Code / other MCP clients

Use the same config as Claude Desktop above. Most MCP clients follow the same schema.

Environment variables

Setup is one env var โ€” every tool (read and write) runs through the secure server-side VibeAds gateway with your API key.

VariableRequired?Purpose
VIBEADS_API_KEYโœ… RequiredYour vba_mcp_... key. This is the only credential any tool needs.
VIBEADS_SUPABASE_URLOptionalOverride the VibeAds backend URL. Defaults to the production endpoint.

Usage

Once configured, you can ask Claude questions like:

๐Ÿ“‹ Campaign discovery

"Show me all my VibeAds campaigns"

"Which campaigns are paused?"

"Give me the 5 most recently created campaigns"

๐Ÿ”ฌ Deep dives

"Tell me everything about my plumber campaign in Austin"

"How did my HVAC campaign perform last week?"

"What's the CPA for campaign abc12345?"

๐Ÿ“Š Account health

"What's my VibeAds account health score?"

"Which dimension is pulling my score down?"

"Give me the health score just for campaign xyz"

๐Ÿ’ธ Search term analysis

"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?"

๐Ÿฉบ Diagnostics + recommendations

"What should I fix first?"

"Show me all critical diagnostics"

"What's wrong with my roofing campaign?"


Available tools

Read tools

ToolPurpose
list_campaignsEnumerate all campaigns with status, budget, category
get_campaign_detailsDeep dive on one campaign: metrics, ad groups, targeting, landing pages, diagnostics
get_account_health_score0-100 score + letter grade across 6 dimensions, optionally per-campaign
get_search_term_analysisWasted spend + winners from search terms report (configurable lookback + threshold)
get_diagnosticsFull 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 (Pro/Max)

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.

ToolPurpose
generate_strategyDraft 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_statusPoll a strategy job: status, phase, and drafted ad groups once complete
apply_strategyTurn 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_recommendationsPending optimization recommendations awaiting approval, with the session + recommendation IDs
approve_recommendationExecute ONE diagnosed optimization inside the safety guardrails; sibling recommendations stay pending
request_publishStart the publish flow for a campaign that has ad groups โ€” returns a human-approval URL because publishing spends real money
check_approvalPoll a publish approval: pending โ†’ approved โ†’ executing โ†’ executed (or rejected / expired / failed)

From idea to live campaign:

  1. generate_strategy drafts the strategy server-side and returns a jobId. Nothing exists in Google Ads yet.
  2. get_strategy_status polls that job until it reports completed.
  3. apply_strategy turns the finished preview into a real draft campaign and returns a campaignId. Still not live, still spending nothing.
  4. request_publish takes that campaignId and returns an approval link.
  5. You open the link in your browser, review the campaign + budget, and click Approve (or Reject).
  6. 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.


Security

  • Read tools are read-only. They cannot mutate your campaigns, your Google Ads account, or your VibeAds settings.
  • Write tools are guarded. Every write action runs server-side inside VibeAds' safety guardrails (blast-radius caps, rate limits, automatic rollback), and publishing always requires a human approving in the browser โ€” the API key can never approve ad spend by itself.
  • Keys are hashed with SHA-256 before storage. The full key is only shown once at creation.
  • Revocable any time from https://getvibeads.com/app/settings/mcp.
  • Usage is logged per-key: last-used timestamp and request count.
  • Row-level isolation โ€” each key is scoped to a single VibeAds user. Keys cannot see other users' data.
  • Optional expiry โ€” set expiration dates on keys for service accounts / temporary access.

For maximum security, rotate your API key whenever a device changes hands or an engagement ends.


Requirements

  • Node.js โ‰ฅ 20 (for npx runtime)
  • Active VibeAds account โ€” free tier is sufficient to generate a key
  • Pro or Max plan โ€” required for the write tools (read tools work on any plan)
  • At least one published campaign โ€” diagnostics require synced data from Google Ads

How it compares

VibeAds MCPGoMarble MCPGoogle Ads MCP (official)
Setup time2 min15 min30 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.


Troubleshooting

"Authentication failed"

"No diagnostic data yet"

Diagnostics are generated every 6 hours by the VibeAds agent. If you just published a campaign, wait 6-12 hours for the first run.

"No search term data found"

Search term sync runs every 6 hours. For new campaigns, allow 24-48 hours for meaningful data to accumulate.

MCP client can't find the server

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.


Contributing

This is an open-source MIT package. Issues and PRs welcome at: https://github.com/vibeads/mcp/issues


License

MIT ยฉ VibeAds