Vibeads MCP Server

Talk to your Google Ads account from Claude Desktop, Cursor, or any MCP client. Built for local service businesses: 35 categories, 32 of them with tuned keywords, CPC benchmarks and funnel templates.

Local serverstdioMIT

What is the Vibeads MCP Server?

vibeads-mcp is an MCP project maintained in the vibeads/mcp repository. The maintainer describes its purpose as “Talk to your Google Ads account from Claude Desktop, Cursor, or any MCP client. Built for local service businesses: 35 categories, 32 of them with…”. Read the project documentation for the complete scope.

Installation

The documented npm package is @vibeads/mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares VIBEADS_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
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 each campaign's latest synced search terms, which cover the 7 days before that sync (configurable cost threshold)
get_diagnosticsLatest agent-optimize diagnostics with severity + recommended fix (up to 50)
find_campaigns_to_importBefore importing: the campaigns in your Google Ads account, read from Google Ads, each marked with whether it is in VibeAds (VibeAds manages only the campaigns
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…
list_recommendationsPending optimization recommendations awaiting approval, with the session + recommendation IDs
approve_recommendationExecute ONE diagnosed optimization. Approving closes its session and rejects the other recommendations in it. A budget increase over 20% returns an approval…
preview_ad_groupShow a new ad group (keywords, three ads, landing page plan) before it is added. Creates a preview only
add_ad_groupAdd a previewed ad group. On a published campaign it starts serving at once, within the campaign's budget
request_publishStart the publish flow for a campaign that has ad groups — returns a human-approval URL because publishing spends real money. With more than one Google Ads…
import_campaignsBring up to 3 campaigns from your Google Ads account into VibeAds, so its optimizer and reports cover them. Nothing changes in Google Ads. 1 credit each
pause_campaignPause a live campaign in Google Ads. Starting it again is done in VibeAds
check_approvalPoll a publish approval: pending → approved → executing → executed (or rejected / expired / failed)

How to install the Vibeads MCP Server

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

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
VIBEADS_API_KEYDeclared in the maintainer’s client configuration.Yes