Skip to main content
Glama

@vibeads/mcp

npm version License: MIT MCP

Talk to your Google Ads account from ChatGPT, Claude, Claude Code, Cursor or any MCP client.

Built for local service businesses: 35 categories, 32 of them with tuned keywords, CPC benchmarks and funnel templates.

The official Model Context Protocol server for VibeAds. Ask your assistant 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, apply guarded optimizations, edit keywords, bids and budgets, add ad groups, and publish, with you confirming anything that spends money.

There are two ways to connect, and both reach the same 29 tools:

  • Sign in (OAuth). In ChatGPT, install VibeAds from ChatGPT's plugin directory (US listing). In Claude, Muse or Claude Code, or in ChatGPT outside the US, add the hosted server, https://getvibeads.com/api/mcp. Then sign in to VibeAds when it asks. No key and nothing to install.

  • API key. For Cursor, Cline, Windsurf and any client that can't sign in: create a vba_mcp_ key and use this npm package, or send the key to the hosted server in a header.


Features

  • 🎯 Local-service-first: 27 home-service verticals plus 8 professional/lead-gen ones; 32 of them have their 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, apply optimizations, edit keywords, bids and budgets, and publish through the VibeAds gateway

  • 🔐 Sign in or use a key: OAuth sign-in for assistants that support it, a revocable API key for everything else. Your Google login never reaches the assistant

  • 🔒 Safe by design: read tools can't modify anything; write tools run inside VibeAds' safety guardrails, and nothing spends money without you confirming it

  • ⚡ No GAQL required: ask questions in natural language, get markdown answers


Related MCP server: Google Ads MCP Server

Supported categories

Local & home services (27): 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 · air duct & dryer vent cleaning · commercial cleaning & janitorial · 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

Consulting, SaaS and B2B services use generic defaults, and so does any other category you pass, instead of a tuned knowledge base.


Connect

Sign in (OAuth)

API key

For

ChatGPT, Claude (claude.ai and Claude Desktop), Muse, Claude Code

Cursor, Cline, Windsurf and any other MCP client (Claude Code too, if you prefer a key)

How

Add https://getvibeads.com/api/mcp; the app opens VibeAds, where you sign in and press Allow access

Create a vba_mcp_ key, then run this package or send the key to the hosted server in a header

Publishing a campaign or starting a paused one

ChatGPT, Claude and Muse: a Search campaign within the daily limit you allow assistants, after you confirm its budget in the chat; anything else gets an approval link. Claude Code: always an approval link

Always an approval link you open in VibeAds

Raising a daily budget

ChatGPT, Claude and Muse: up to 20% in the chat; more gets an approval link. Claude Code: always an approval link

Always an approval link

Stopping it

Settings, Connected apps: Disconnect

Settings, MCP Server Keys: Revoke

Rate limit

60 calls an hour, shared by the apps you signed in to

60 calls an hour per key

An approval link only works in your own signed-in VibeAds session, so neither a key nor a connected app can approve it.

Option A: sign in (no key, nothing to install)

ChatGPT, Claude and Muse

In ChatGPT in the US, install VibeAds from the plugin directory: open Plugins, search for VibeAds and press Install plugin. Elsewhere, add the server address as a custom connector (Claude, Muse) or a custom MCP server (ChatGPT outside the US). Sign in to VibeAds when the assistant asks:

https://getvibeads.com/api/mcp

Step-by-step instructions for each one: Connect ChatGPT, Claude or Muse. VibeAds emails you when an app is connected to your account.

Claude Code

Add the server with a fixed callback port, then open /mcp in Claude Code, choose VibeAds and sign in in your browser:

claude mcp add --transport http --callback-port 31790 vibeads https://getvibeads.com/api/mcp

Any free port works; 31790 is an example. Keep it fixed: VibeAds checks the return address exactly, so a later sign-in on a different port is refused (run claude mcp remove vibeads and add it again). VibeAds' sign-in page calls Claude Code "An app on this computer": allow it only if you just started connecting from Claude Code.

Signed-in apps are listed in Settings, Connected apps, where you can disconnect them and set the daily budget assistants may publish up to.

Option B: API key

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_, are shown once, and are scoped to your account only. Make one per client or machine, so you can revoke one without touching the others.

Step 2: configure your MCP client

This package runs on your computer and forwards every call to VibeAds with your key. It always uses an API key; to sign in instead, use Option A.

Claude Desktop

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:

{
  "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. (Claude Desktop can also sign in instead, through a custom connector: see Option A.)

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

Claude Code
claude mcp add vibeads -e VIBEADS_API_KEY=vba_mcp_YOUR_KEY_HERE -- npx -y @vibeads/mcp
Cline and other MCP clients

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

npx -y @vibeads/mcp --init prints ready-to-paste configs for each client.

Or: the hosted server with your key

Nothing to install: give the client the hosted address and send the key in an x-vibeads-api-key header. In Claude Code:

claude mcp add --transport http vibeads https://getvibeads.com/api/mcp --header "x-vibeads-api-key: vba_mcp_YOUR_KEY_HERE"

The key also works as Authorization: Bearer vba_mcp_.... A client that can't send headers can put it in the address (https://getvibeads.com/api/mcp?key=vba_mcp_...); that address then works like a password, so prefer a header or signing in. Guides for Cursor, OpenAI Codex, Gemini CLI and VS Code with GitHub Copilot.

Environment variables (this package)

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

Variable

Required?

Purpose

VIBEADS_API_KEY

✅ Required

Your vba_mcp_... key. It is the only credential the package needs.

VIBEADS_SUPABASE_URL

Optional

Override the VibeAds backend URL. Defaults to the production endpoint.


Usage

Once connected, you can ask your assistant 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?"

📈 Reports for any period

"Compare September with August for my Austin plumbing campaign"

"Spend by device across my whole account last month"

"Which keywords spent the most in the last 90 days?"

🔎 Keyword research

"How many people search for drain cleaning in Austin, TX?"

"Find keyword ideas from my services page for Round Rock and Pflugerville"

🧾 Audit a whole Google Ads account

Works right after you connect Google Ads, before anything is imported:

"Where is my Google Ads budget being wasted?"

"Audit my Google Ads account"

📊 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

Tool

Purpose

list_campaigns

Your campaigns in VibeAds (published, imported and drafts) with status, budget and category. Campaigns only in your Google Ads account are listed by find_campaigns_to_import

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 each campaign's latest synced search terms, which cover the 7 days before that sync (configurable cost threshold)

get_diagnostics

Latest agent-optimize diagnostics with severity + recommended fix (up to 50)

find_campaigns_to_import

Before 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 in it). Called list_google_ads_campaigns in 0.2.15

get_performance_report

One campaign's or a whole account's figures for a period you choose (a preset or two dates, up to 90 days), read live from Google Ads, optionally by day, device, hour, ad group, keyword or location. Money in the account's currency. VibeAds builds every query; the assistant only picks the period and the breakdown

audit_google_ads_account

An audit of one connected Google Ads account, read live from Google Ads: up to 25 Search campaigns over the last 30 days, whether or not they are in VibeAds, with a 0-100 health score and grade for the account and each campaign, the issues grouped by check with what fixes each in Google Ads, and each campaign's costliest search terms with clicks and no conversions. One audit per account is kept for 24 hours

list_keywords

One published campaign's ad groups, keywords and negative keywords, read live from Google Ads: match type, status, max CPC and 30 days of clicks, cost and conversions

research_keywords

Keyword ideas from Google's Keyword Planner for seed keywords, a web page or both, in the places you name: average monthly searches, competition and top-of-page bid range. Pro/Max, 2 credits (a repeat within 90 days is free)

list_google_ads_accounts

Every connected Google Ads account, switched on or not, with the manager account (MCC) each client account sits under

list_google_recommendations

Google's own recommendations for an account (its Recommendations page), with Google's estimate and whether each can be applied from the chat

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, the same whether you signed in or use a key. Read tools work on any plan, free tier included, except research_keywords, which needs Pro or Max.

Write tools (Pro/Max)

Write tools run on the server-side VibeAds gateway, with a sign-in or an API key and nothing else (no Supabase or Google keys). Every call is rate-limited, approved optimizations are measured afterwards (smaller changes roll back automatically if metrics worsen), and nothing that spends money happens without you confirming it: an API key, or Claude Code signed in, gets an approval link you open in VibeAds; ChatGPT, Claude and Muse publish only within the daily limit you allow assistants, after you confirm the budget in the chat.

Tool

Purpose

generate_strategy

Draft a full campaign strategy (keywords, ad copy, 3+ ad groups) server-side, and on Max an ad group for each competitor you name. 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, each with the tool and exact arguments that carry it out (its session and recommendation IDs included), or a link to approve it in VibeAds when no tool makes that change

preview_ad_group

Show a new ad group (keywords, three ads, landing page plan) before it is added. Creates a preview only

add_ad_group

Add a previewed ad group. On a published campaign it starts serving at once, within the campaign's budget

request_publish

Publish a campaign that has ad groups. Publishing spends real money, so with an API key or Claude Code it returns a human-approval URL; ChatGPT, Claude and Muse publish a Search campaign within the daily limit you allow assistants once you confirm its budget in the chat, and get an approval URL otherwise. With more than one Google Ads account it asks which one, and publishes to that one only

import_campaigns

Bring 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_campaign

Pause a live campaign in Google Ads

resume_campaign

Start a paused campaign again, under the same rules as publishing: with an API key or Claude Code it returns a human-approval URL

add_negative_keywords

Add up to 20 negative keywords to a campaign or one ad group, at once. One that would block the campaign's own keywords is left out

add_keywords

Add up to 20 keywords to one ad group, at once, at the ad group's default max CPC

set_keyword_status

Pause keywords, or turn paused ones back on

set_max_cpc

Set an ad group's, a keyword's or a list of keywords' max CPC on a Manual CPC campaign. Up to double and $50 a click at once; more returns an approval URL

set_daily_budget

Set a campaign's daily budget. A decrease runs at once. An increase returns an approval URL with an API key or Claude Code; signed in to ChatGPT, Claude or Muse, up to 20% runs at once

dismiss_google_recommendation

Remove one of Google's recommendations from its list. No campaign changes

check_approval

Poll a publish or change approval: pending → approved → executing → executed (or rejected / expired / failed)

Every keyword, bid, budget and restart change is listed on the campaign's Optimize tab in VibeAds, where it can be undone. VibeAds never rolls these back by itself. An assistant can make 20 changes to a campaign a day.

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. With an API key or Claude Code it returns an approval link.

  5. You open the link in your browser, signed in to VibeAds, review the campaign and its budget, and click Approve (or Reject).

  6. check_approval reports the approval and then the publish job; the campaign is live once that job completes.

Steps 1–3 create rows only in VibeAds and spend VibeAds credits (13 for step 1; 6 + 3 per ad group for step 3). With an API key, step 5 is the only point where ad money is committed, and it can only happen in your browser: the key alone can never publish, so a leaked key still cannot spend.

ChatGPT, Claude and Muse, connected by signing in, skip the link for a Search campaign whose daily budget is within the limit you allow assistants ($100 a day unless you change it or turn it off, in VibeAds Settings under Connected apps): in step 4 the assistant tells you the daily budget, and publishes only after you confirm it in the chat. VibeAds emails you when the campaign is live. A bigger campaign gets the approval link.


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 through the VibeAds gateway, rate-limited to 60 calls an hour. Approved optimizations are measured afterwards, and smaller changes roll back automatically if metrics worsen. Every keyword, bid, budget and restart change an assistant makes is listed on the campaign's Optimize tab in VibeAds, where you can undo it.

  • Spending needs you. An approval link only works in your own signed-in VibeAds session, so neither a key nor a connected app can approve one. An API key, or Claude Code signed in, can never publish, restart a campaign or raise a budget by itself.

  • Your Google login stays with VibeAds. Google Ads connects to VibeAds once, through Google's own sign-in. A key or a signed-in app only ever reaches VibeAds; your Google tokens never reach the assistant or your computer.

Signing in (OAuth)

  • OAuth 2.1 authorization code with PKCE. VibeAds' sign-in page shows which app is asking and what it may do, and you press Allow access.

  • Outside these tools, VibeAds refuses a signed-in app anything that changes your account, and never lets it see your Google Ads login.

  • VibeAds emails you when an app is connected to your account.

  • Disconnect any app in Settings, Connected apps; it is signed out at once.

API keys

  • Keys are hashed with SHA-256 before storage. The full key is only shown once at creation.

  • Revocable any time from Settings, MCP Server Keys.

  • Usage is logged per key: last-used date and request count.

  • Each key is scoped to a single VibeAds user and cannot see other users' data.

For maximum security, revoke and replace an API key whenever a device changes hands or an engagement ends.


Requirements

  • Active VibeAds account: sign-in and keys work on every plan, the free plan included

  • Pro or Max plan: needed for the write tools (read tools work on any plan)

  • Google Ads connected to VibeAds: for live numbers, importing and publishing. Connect it in VibeAds Settings, or from the link the assistant gives you when it needs it

  • At least one published or imported campaign: diagnostics need synced data from Google Ads

  • Node.js ≥ 20: only for this npm package (npx runs it); signing in or using the hosted server needs nothing installed


How it compares

VibeAds MCP

GoMarble MCP

Google Ads MCP (official)

Setup time

2 min

15 min

30 min

How you connect

Sign in to VibeAds (OAuth) or an API key; Google Ads connects once inside VibeAds

Google OAuth

Google OAuth

GAQL knowledge required

❌

✅

✅

Local service tuning

✅

❌

❌

Account health score

✅ 6 dimensions

❌

❌

Pre-built diagnostics

✅ 35+ rules

❌

❌

Multi-account

✅

✅

✅

Guarded write actions

✅ you confirm anything that spends

❌

❌

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

"API key is invalid" or "Authentication failed"

"Missing VibeAds API key" (hosted server with a key)

The header name must be exactly x-vibeads-api-key, and the key must start with vba_mcp_. Or remove the header and sign in instead.

The assistant asks you to sign in again, or says it isn't connected

The app was disconnected in Settings, Connected apps, or its sign-in ended. Connect it again from the assistant (ChatGPT: Settings, Plugins, VibeAds; Claude: Customize, Connectors; Claude Code: /mcp) and sign in.

Claude Code: the sign-in is refused

Claude Code was added without a fixed callback port, or with a different one. Run claude mcp remove vibeads, add it again with --callback-port (see Option A), and sign in from /mcp.

"No optimizer diagnoses yet"

Diagnostics are generated every 12 hours by the VibeAds agent, once Google Ads performance has synced. If you just published a campaign, allow up to a day 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 (npm package)

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

Available Tools

11 tools
approve_recommendationAInspect

Approve and execute ONE already-diagnosed optimization recommendation inside VibeAds' safety guardrails (blast-radius caps, rate limits, auto-rollback if metrics worsen). Other pending recommendations on the session stay pending — approving one never rejects or executes the rest.

Inputs: sessionId (required), recommendationId (required).

check_approvalAInspect

Check the status of a publish approval created with request_publish. Status is one of: pending, approved, rejected, expired, executing, executed, failed. While pending, remind the user to open the approval link in their browser — approval cannot happen through the API. Once executed, the campaign is live in Google Ads and serving ads immediately (it is not paused) — tell the user it is now spending, and that they can pause it from the dashboard.

Inputs: approvalId (required).

generate_strategyAInspect

Preview a DRAFT campaign strategy server-side: keywords, ad copy, and 3+ ad groups tailored to a service category, budget, and locations. Costs 13 VibeAds credits. Returns a jobId — poll get_strategy_status with that jobId. IMPORTANT: this is a preview only. It does NOT create a publishable campaign, so request_publish cannot act on it; the user applies the draft at https://getvibeads.com/app/new-campaign to turn it into a real campaign. Nothing is published and no ad money is spent.

Inputs: category (required), budget, locations, businessName.

get_account_health_scoreAInspect

Compute a 0-100 account health score across 6 dimensions (Tracking, Keywords, Budget, Creative, Targeting, Performance) by rolling up the latest diagnostics from all campaigns. Returns a letter grade A-F and per-dimension breakdown. Optionally scope to a single campaign.

Inputs: campaign_id.

get_campaign_detailsAInspect

Get a detailed view of a single VibeAds campaign: budget, bidding strategy, ad groups, targeted locations, landing pages, last 7 days of performance metrics (impressions, clicks, CTR, CPC, spend, conversions, CPA), and any active diagnostics.

Inputs: campaign_id (required).

get_diagnosticsAInspect

Return the full list of active diagnostics across all campaigns with severity (critical / high / medium / low), affected metric, current value vs benchmark, and recommended action. Can filter by severity and scope to a specific campaign.

Inputs: limit, severity, campaign_id.

get_search_term_analysisAInspect

Analyze search terms from the last N days to find wasted spend (high-cost terms with zero conversions) and winning terms (high conversion rate). Returns a ranked list of terms to negate plus positive terms worth doubling down on. Can be scoped to a single campaign.

Inputs: min_cost, campaign_id, lookback_days.

get_strategy_statusAInspect

Poll the status of a strategy generation job started with generate_strategy. Returns status and phase while running, and the drafted ad groups (with keyword and headline counts) once complete. Poll every 10-15 seconds until status is completed or failed. The finished draft is a preview: show it to the user and point them to https://getvibeads.com/app/new-campaign to apply it as a real campaign — request_publish cannot publish a preview.

Inputs: jobId (required).

list_campaignsAInspect

List all Google Ads campaigns managed by VibeAds for the authenticated user. Returns name, status, category, budget, and high-level metadata. Use this first to discover which campaigns exist before drilling in.

Inputs: limit, status.

list_recommendationsAInspect

List pending optimization recommendations awaiting approval, grouped by optimization session. Each recommendation includes action, reason, risk level, blast radius, auto-eligibility, and estimated impact, plus the sessionId + recommendationId needed for approve_recommendation. Optionally scope to one campaign.

Inputs: campaignId.

request_publishAInspect

Start the publish flow for an EXISTING campaign (one that already has ad groups — find it with list_campaigns; a generate_strategy preview does not qualify). Publishing spends real money, so this returns a human-approval URL instead of publishing directly — SHOW the approvalUrl to the user and ask them to open it in their browser, review the budget, and approve — on approval the campaign goes LIVE immediately and can start spending its daily budget. The API key cannot approve a publish. After the user approves, poll check_approval with the returned approvalId.

Inputs: campaignId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: listing vs details, analysis types (health, search terms, diagnostics), strategy generation and polling, recommendations list/approve, publish and approval check. No two tools appear to overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (list_, get_, generate_, approve_, request_, check_), with clear object nouns. Minor compound names don't break the pattern.

    Tool Count5/5

    11 tools is well-scoped for a Google Ads management server, covering discovery, analysis, strategy, recommendations, and publishing without bloat. Each tool addresses a distinct stage in the workflow.

    Completeness4/5

    The set covers the full lifecycle of analyzing, optimizing, and publishing campaigns. Gaps like creating/pausing campaigns are intentionally delegated to the web UI, so agents can still navigate the core workflow, but direct CRUD beyond reading/publishing is missing.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with the Google Ads API through the Model Context Protocol, allowing natural language queries for campaign management and metrics.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that exposes the Google Ads API to LLM clients, enabling account inspection, GAQL queries, performance reporting, and campaign management.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLMs and AI agents to query and explore Google Ads accounts and API resources through MCP tools and resources, including account information, resource metadata, metrics, segments, and release notes.
      3
      Apache 2.0