AI-powered advertising management MCP server — 180+ tools across Google Ads, Meta Ads, GA4, Search Console, Matomo, and Bing Webmaster Tools
{
"mcpServers": {
"aidvertaiser": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AI-powered advertising management MCP server — 180+ tools across Google Ads, Meta Ads, GA4, Search Console, Matomo, and Bing Webmaster Tools
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 5 days ago. 8 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for Aidvertaiser and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
| 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) |
# From source
git clone https://github.com/Draivix/aidvertaiser.git
cd aidvertaiser
uv sync
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
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.
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
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
Uses google-ads.yaml for client credentials (same Google Cloud project). No separate config needed.
Also provides the Indexing API for submitting URLs. Requires the Web Search Indexing API enabled in Google Cloud Console.
Create ~/.unified-ads-mcp/google-tagmanager.yaml:
client_id: YOUR_CLIENT_ID
client_secret: YOUR_CLIENT_SECRET
default_account_id: YOUR_GTM_ACCOUNT_ID # Optional
default_container_id: YOUR_GTM_CONTAINER_ID # Optional
Falls back to google-ads.yaml for client_id/client_secret.
Env var override: GOOGLE_TAGMANAGER_CREDENTIALS=/path/to/google-tagmanager.yaml
Create ~/.unified-ads-mcp/matomo.yaml:
url: https://your-matomo-instance.com
token_auth: YOUR_API_TOKEN
default_site_id: 1 # Optional
Env var override: MATOMO_CREDENTIALS=/path/to/matomo.yaml
Create ~/.unified-ads-mcp/bing-webmaster.yaml:
api_key: YOUR_API_KEY
default_site_url: https://yoursite.com # Optional
Get the API key from: Bing Webmaster Tools > Settings > API Access > Generate API Key.
Env var override: `BING_WEBMASTER_CREDENTI