# Google Ads + Meta Ads + GA4 MCP [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/irinabuht12-oss/google-meta-ads-ga4-mcp  
**GitHub Stars:** 6153  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-ads-meta-ads-ga4-mcp

## Description
Google Ads, Meta Ads & GA4 MCP server - 250+ tools for campaigns, creatives, audiences & reports.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Google Ads + Meta Ads + GA4 MCP does

Google Ads + Meta Ads + GA4 MCP brings advertising and analytics operations into one remote MCP endpoint. It exposes the Google Ads API, Meta Marketing API, and Google Analytics 4 Data API as tools that an MCP-compatible assistant can call. The repository also identifies Google Search Console as part of the broader connector.

The tool set covers more than 250 operations: over 150 for Google Ads, more than 80 for Meta Ads, and more than 20 for GA4. Supported workflows include reviewing campaign performance, researching keywords, creating or changing campaigns, uploading creatives, building audiences, and retrieving reports. GA4 capabilities include standard reporting, realtime data, and analysis of traffic referred by AI services.

## How it works

The service runs remotely over Streamable HTTP at `https://connector.get-ryze.ai/mcp`; nothing needs to run on the user's machine. An MCP client connects to that endpoint, then the user signs in with the Google or Facebook account that has access to the relevant advertising accounts. Authentication uses OAuth 2.1 with PKCE.

Read operations can be requested directly through the connected assistant. Changes such as budget updates, bid changes, pausing campaigns, creating campaigns, and modifying keywords are staged for approval before they are applied. Google Ads users can retrieve accessible customers and provide `customerId` for calls; manager-account workflows can also provide `loginCustomerId`. Meta account access is handled through available ad accounts.

## Setup and configuration

Claude Code can add the endpoint with:

```bash
claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp
```

For claude.ai, Claude Desktop, ChatGPT, and Cursor, the connection flow is to open the client's connector settings, choose the option to add a custom connector, enter the same URL, and complete the Google or Facebook OAuth login. The hosted connection requires no local package installation, Google Ads developer token, Meta app, or API key.

The service is offered through Ryze plans and includes a seven-day free trial. Its documented Paid Ads plan is listed at $89 per month.

## Tools and capabilities

- Query Google Ads accounts, campaigns, keywords, budgets, bids, and performance data.
- Work with Meta advertising accounts across Facebook and Instagram placements.
- Research keywords and create or update advertising campaigns.
- Upload and manage ad creatives and build audience definitions.
- Generate Google Ads, Meta Ads, and GA4 reports.
- Query GA4 realtime data and investigate referrals from ChatGPT, Claude, Gemini, and Perplexity.
- Use one endpoint for cross-platform advertising and analytics workflows.

## Limitations and notes

This is a hosted service rather than a self-hosted local server, so the connection depends on the remote Ryze endpoint and its account-based access model. Write actions are not applied immediately: each proposed change must pass through the approval step. Google Ads access is account-scoped, with `customerId` required for calls and `loginCustomerId` relevant to manager accounts. The repository positions this server for users who want read and write access across several platforms; Google's official MCP server remains a separate, local, read-only alternative.

_Full upstream README: https://allmcps.com/mcp/google-ads-meta-ads-ga4-mcp/readme_