DA

draivix/aidvertaiser

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

21 stars 7 forks Качество 58 Тренд 18

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

Обзор

AI-powered advertising management via MCP. 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. Add to your MCP client config (e.g. ~/.claude/mcp_servers.json): All config files live in ~/.unified-ads-mcp/. Create this directory first: OAuth tokens are cached here automatically after first browser-based authentication. Create ~/.unified-ads-mcp/google-ads.yaml: GOOGLE_ADS_CREDENTIALS=/path/to/google-ads.yaml Set ONLY_DEFAULT_ACCOUNT=1 to disable google_list_accounts and force using the default customer ID everywhere. Useful when you only manage one account.

README

Показан фрагмент оригинального README. Открыть оригинал.

Aidvertaiser

AI-powered advertising management via MCP. 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.

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 account.

Meta Ads

Create ~/.unified-ads-mcp/meta-ads.yaml:

app_id: YOUR_APP_ID
app_secret: YOUR_APP_SECRET
access_token: YOUR_TOKEN              # Optional, bypasses browser OAuth
default_account_id: act_XXXXXXXXXX    # Optional

Or set environment variables: META_APP_ID, META_APP_SECRET, META_ACCESS_TOKEN.

Env var override: META_ADS_CREDENTIALS=/path/to/meta-ads.yaml

Google Analytics (GA4)

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

client_id: YOUR_CLIENT_ID
client_secret: YOUR_CLIENT_SECRET
default_property_id: YOUR_PROPERTY_ID   # Optional

Falls back to google-ads.yaml for client_id/client_secret (same Google Cloud project).

Env var override: GOOGLE_ANALYTICS_CREDENTIALS=/path/to/google-analytics.yaml

Google Search Console

Uses google-ads.yaml for client credentials (same Google Cloud project). No separate config needed.

Открыть полный README на GitHub

Установка

This server does not publish a one-line install command.

Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →