Draivix

Aidvertaiser — AI skill for Claude Code

AI community

AI-powered advertising management MCP server — 180+ tools across Google Ads, Meta Ads, GA4, Search Console, Matomo, and Bing Webmaster Tools.

How to install Aidvertaiser

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Draivix/aidvertaiser and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Aidvertaiser does

AI-powered advertising management MCP server — 180+ tools across Google Ads, Meta Ads, GA4, Search Console, Matomo, and Bing Webmaster Tools.

Alternatives in AI

Codeseek — Rust-powered code intelligence CLI for AI coding agents 764 ★
Metaharness — 🛠️ The meta-harness for AI agents — scaffold your own focused, branded agent harness with its own npx CLI, MC 616 ★
Obsidian + Claude Code: Rebuild Your Second Brain With AI — Build an AI-powered personal knowledge management system from scratch 540 ★

README

Aidvertaiser

AI-powered advertising management via [MCP](https://modelcontextprotocol.io). 232 tools across 8 platforms — Google Ads, Meta Ads, GA4, Search Console, Tag Manager, Matomo, Bing Webmaster, and PageSpeed Insights.

Open source. One server. Works with Claude, Cursor, Windsurf, and any MCP client.

Platforms

Platform	Prefix	Tools	Auth
Google Ads	`google_`	81	OAuth (browser)
Meta Ads	`meta_`	40	OAuth (browser)
Google Analytics (GA4)	`ga4_`	31	OAuth (browser)
Google Search Console	`gsc_`	18	OAuth (browser)
Google Tag Manager	`gtm_`	14	OAuth (browser)
Matomo Analytics	`matomo_`	24	API token
Bing Webmaster Tools	`bing_`	21	API key
PageSpeed Insights	`pagespeed_`	3	API key (optional)

Installation

# From source
git clone https://github.com/Draivix/aidvertaiser.git
cd aidvertaiser
uv sync

Quick Start

Add to your MCP client config (e.g. `~/.claude/mcp_servers.json`):

{
  "aidvertaiser": {
    "command": "uv",
    "args": ["run", "--directory", "/path/to/aidvertaiser", "unified-ads-mcp"]
  }
}

Or run directly:

uv run unified-ads-mcp

Configuration

All config files live in `~/.unified-ads-mcp/`. Create this directory first:

mkdir -p ~/.unified-ads-mcp

OAuth tokens are cached here automatically after first browser-based authentication.

Google Ads

Create `~/.unified-ads-mcp/google-ads.yaml`:

developer_token: YOUR_DEVELOPER_TOKEN
client_id: YOUR_CLIENT_ID
client_secret: YOUR_CLIENT_SECRET
login_customer_id: YOUR_MCC_ID          # Optional, for MCC access
default_customer_id: YOUR_CUSTOMER_ID   # Optional, skip account listing

**Env var override:** `GOOGLE_ADS_CREDENTIALS=/path/to/google-ads.yaml`

**Tip:** Set `ONLY_DEFAULT_ACCOUNT=1` to disable `google_list_accounts` and force using the default customer ID everywhere. Useful when you only manage one a