irinabuht12-oss/google-meta-ads-ga4-mcp

Add the remote endpoint URL to your client config: { "mcpServers": { "google-meta-ads-ga4": { "url": "YOUR_MCP_ENDPOINT_URL" } } }
claude mcp add google-meta-ads-ga4 --transport sse YOUR_MCP_ENDPOINT_URL

Usage

• •Connect ad accounts via OAuth on first use (no API keys to manage)
• •Ask e.g. "Show me all my Google Ads campaigns and their performance this month", "Create a new Search campaign targeting 'best CRM software'", "Compare my Google Ads and Meta Ads ROAS for Q1 2026"
• •n8n: use the MCP Client node with Streamable HTTP and Bearer auth

Key features

• ✓150+ Google Ads tools: campaign CRUD (Search/Display/Shopping/PMax/Demand Gen/Video/App), keyword planner, bidding/budgets, extensions, experiments, conversion tracking
• ✓80+ Meta Ads tools: campaign/ad set/ad CRUD, creatives & media upload, audiences/lookalikes, lead forms, product catalogs, boosts, business management
• ✓20+ GA4 tools: standard/pivot/realtime reports, audiences, key events, attribution, BigQuery/DV360/Firebase links
• ✓Cross-platform ROAS comparison and budget-allocation recommendations
• ✓OAuth 2.1 with PKCE; no data storage (tokens stay on your machine); read-only by default with write confirmation

Caveats

• ⚠Hosted remote MCP service (endpoint URL required); powered by Ryze AI
• ⚠Write operations require explicit confirmation; scoped access
• ⚠You pay for the AI assistant you use plus ad spend; the MCP server itself is free