google-meta-ads-ga4-mcp
An MCP server providing unified access to Google Ads, Meta Ads, and Google Analytics 4 APIs through a single interface, exposing 250+ tools for campaign management and analytics. Integrates with ChatGPT, Claude, Cursor, n8n, Windsurf, and other AI assistants.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | irinabuht12-oss/google-meta-ads-ga4-mcp |
| Owner | irinabuht12-oss |
| Primary language | Unknown |
| License | MIT — OSI-approved |
| Stars | 1k |
| Forks | 46 |
| Open issues | 3 |
| Latest release | Unknown |
| Last updated | 2026-04-07 |
| Source | https://github.com/irinabuht12-oss/google-meta-ads-ga4-mcp |
What google-meta-ads-ga4-mcp is
Implements Model Context Protocol (MCP) as a remote endpoint, wrapping Google Ads API v20, Meta Marketing API, and GA4 Data API. Supports read and write operations across campaigns, audiences, creatives, and analytics with credential-based authentication.
Get the google-meta-ads-ga4-mcp source
Clone the repository and explore it locally.
git clone https://github.com/irinabuht12-oss/google-meta-ads-ga4-mcp.gitcd google-meta-ads-ga4-mcp# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires valid OAuth 2.0 credentials for Google Ads, Meta Ads, and GA4 properties; credential management and rotation strategy needed before production use.
- MCP endpoint URL and authentication method (Bearer token implied) must be securely configured in each AI assistant client; no details provided on credential storage or rotation.
- API rate limits and quota management across Google, Meta, and GA4 are not documented; implementation should include throttling and error handling for quota exhaustion.
- Tool count (250+) is not itemized in README; actual coverage and parameter support for each API endpoint requires hands-on testing or source code review.
- No mention of versioning strategy, backward compatibility, or API deprecation handling as platform APIs evolve.
When to avoid it — and what to weigh
- Offline or air-gapped deployments required — This is a remote MCP endpoint requiring internet connectivity to GitHub/Ryze AI infrastructure and the advertising APIs. Not suitable for fully offline marketing operations.
- Real-time bidding or sub-second performance needs — MCP is request-response; latency through AI assistants and remote endpoint is not optimized for high-frequency algorithmic bidding or millisecond-level campaign changes.
- Complete infrastructure control or data residency mandates — Running as a remote service means credentials and campaign data flow through Ryze AI endpoints. Organizations requiring strict data residency or fully self-hosted solutions should avoid.
- Complex custom business logic or proprietary integrations — Limited documentation on extensibility; if you need heavy customization beyond the 250 exposed tools, self-hosting and modifying source code would be required (source not provided in DATA).
License & commercial use
Licensed under MIT (MIT License). Permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions (attribution required in license/copyright notice).
MIT license permits commercial use. However, the tool integrates with third-party APIs (Google, Meta, GA4) that have their own terms of service. Verify that your use case complies with Google Ads API ToS, Meta Marketing API ToS, and GA4 Data API ToS—especially regarding automated campaign modifications and data usage.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | Medium |
No security audit, threat model, or penetration testing results provided. Key considerations: (1) Credentials for three advertising platforms flow through remote MCP endpoint—verify encryption in transit and at rest; (2) No mention of input validation or injection protection in tool calls; (3) Scope of OAuth 2.0 permissions unclear; (4) No rate limiting or abuse detection documented; (5) Data residency and compliance (GDPR, CCPA) handling not addressed; (6) Dependency vulnerabilities and supply chain risk not disclosed. Requires security review before connecting production ad accounts.
Alternatives to consider
Official Google Ads MCP (Google)
Native, official support for Google Ads only; read-only access; no Meta Ads or GA4 integration, but benefits from Google-backed security and maintenance.
Meta Ads Manager API + n8n native integrations
Self-hosted n8n workflows using Meta's official API connector; requires manual setup per platform but offers full control and no third-party MCP dependency.
Zapier / Make (formerly Integromat)
Fully managed, no-code platform with pre-built connectors for Google Ads, Meta Ads, and GA4; different pricing model but stronger SLA and user support.
Build on google-meta-ads-ga4-mcp with DEV.co software developers
Review the setup guides for your AI assistant (Claude, ChatGPT, Cursor, n8n, Windsurf) and test with a read-only audit workflow before connecting production accounts.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
google-meta-ads-ga4-mcp FAQ
Can I run this MCP server on-premise or self-host?
What happens if the remote MCP endpoint goes down?
Are credentials stored or logged by Ryze AI?
Which API versions are supported (Google Ads v20, etc.)?
Work with a software development agency
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If google-meta-ads-ga4-mcp is part of your mcp servers roadmap, our team can implement, customize, migrate, and maintain it.
Ready to unify your ad management?
Review the setup guides for your AI assistant (Claude, ChatGPT, Cursor, n8n, Windsurf) and test with a read-only audit workflow before connecting production accounts.