Google Ads + Meta Ads + GA4 MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow third-party API versions and account scopes because analytics integrations change quickly

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Marketing teams analyzing and operating Google Ads, Meta Ads, GA4 and Search Console.

What we know

A hosted MCP connector for advertising and analytics research with OAuth and approval-gated write actions.

Maintenance / activity evidence

Observed Sep 25, 2026 (UTC)Repo renamed to google-ads-meta-ads-mcp: update links, server.json 1.2.1

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Account-scoped advertising and analytics permissions. Writes: Campaign, creative and audience writes are described as approval-gated.
Google/Facebook OAuth
Sensitive access: Ad accounts, Analytics, Audiences

A hosted connector can read and modify advertising accounts; OAuth scopes and approval controls are material.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

4,091 repository stars

Stars observed Oct 6, 2026.

No attributable package-download metric.

All limitations / Review context

Which advertising and analytics operations remain available under the documented scopes?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

A hosted connector can read and modify advertising accounts; OAuth scopes and approval controls are material.
Account-scoped advertising and analytics permissions.
Google/Facebook OAuth
Queries and operations pass through a hosted connector.
Reviewed write actions: Campaign, creative and audience writes are described as approval-gated
Sensitive access: Ad accounts, Analytics, Audiences
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Hosted-service dependency.
OAuth scopes and write approval behavior should be checked before production use.

Original activity observations

2026-09-25T23:37:22Z: Repo renamed to google-ads-meta-ads-mcp: update links, server.json 1.2.1

Technical identity

github.com/irinabuht12-oss/google-meta-ads-ga4-mcp

Exact implementation source: https://github.com/irinabuht12-oss/google-meta-ads-ga4-mcp ↗
Reviewed resource type: MCP Server
Repository identity: irinabuht12-oss/google-ads-meta-ads-mcp
Service endpoint: https://connector.get-ryze.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
irinabuht12-oss/google-ads-meta-ads-mcp
Recorded repository material and project history.
Repository document ↗
irinabuht12-oss/google-meta-ads-ga4-mcp
Recorded repository material and project history.
Evidence source ↗
www.get-ryze.ai/google-ads-mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.get-ryze.ai/meta-ads-mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

claude_code_cli

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Publisher hosts the MCP; connectivity and OAuth/account permissions depend on Ryze and the chosen client.
The original Radar identity uses the former GitHub repository name; current publisher repository is `irinabuht12-oss/google-ads-meta-ads-mcp`. Preserve original identity/slug and do not treat as a second candidate.
The provider offers read and write advertising operations. Use read-only commands to verify; writes can affect spend and campaigns and should require explicit review/approval.
Service pricing, trial terms and supported tool counts can change; consult the publisher rather than hardcoding financial claims.
Do not misclassify this host/client/catalog/SDK/complex service as an independently installable standard stdio MCP server.
Could not retrieve the canonical repository README directly; linked official Setup guide consulted instead.
This publisher example belongs to Cursor/Windsurf remote MCP config; not a Claude Desktop local JSON setup and not Codex TOML.
Add remote MCP server in ~/.codex/config.toml using official example; do not use claude mcp CLI in Codex
The `claude mcp remove` command is a generic Claude Code client operation, not a publisher-provided uninstall command. Do not delete business data or ad campaigns.
Canonical roster points to sibling repository github.com/irinabuht12-oss/google-meta-ads-ga4-mcp; publisher also documents same Ryze endpoint at github.com/irinabuht12-oss/google-ads-meta-ads-mcp. Preserve exact identity and do not silently merge repository identities.
MCP100 client-scope note: this Claude Code example applies only to that client and the exact registered entry. Other client configuration keys and registrations are separate.

Install / connect
Publisher instructions
Hosted Ryze Google Ads + Meta Ads + GA4 MCP: `claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp` (publisher README); Claude Desktop/claude.ai: Settings > Connectors > Add custom connector, URL https://connector.get-ryze.ai/mcp. No local npm package.
claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp
Configure / authenticate
Publisher instructions
First use prompts OAuth sign-in with the Google or Meta account with access to the relevant advertising properties; vendor operates hosted OAuth and no user developer token is needed.
Authentication: OAuth via Ryze; Google or Facebook sign-in; vendor-hosted connector
Endpoint: https://connector.get-ryze.ai/mcp
Transport: streamable_http
Claude Desktop and claude.ai: Settings > Connectors > Add custom connector; URL https://connector.get-ryze.ai/mcp; complete OAuth
Codex CLI: Add remote MCP server in ~/.codex/config.toml using official example; do not use claude mcp CLI in Codex
Advanced configuration · cursor mcp json · Publisher instructions
cursor mcp json · Publisher instructions
{ "mcpServers": { "google-meta-ads-ga4": { "url": "https://connector.get-ryze.ai/mcp" } } }
Advanced configuration · Codex CLI · Publisher instructions
Codex CLI · Publisher instructions
[mcp_servers.google-meta-ads-ga4] type = "url" url = "https://connector.get-ryze.ai/mcp"
Check connection
Publisher instructions
Run `claude mcp list` to verify the `ryze` registration exists. Then ask for Google Ads account listing / Meta ad account listing, or GA4 properties, to verify authorized tools; listing only does not confirm OAuth success.
claude mcp list
Remove / uninstall / revoke
MCP100 setup guide
Remove the `ryze` registration from the Claude Code client (`claude mcp remove ryze`, using the standard client CLI); for GUI clients delete/disconnect the Ryze custom connector. This only disconnects the MCP registration; it does not delete third-party ad accounts or necessarily revoke OAuth grants.
The `claude mcp remove` command is a generic Claude Code client operation, not a publisher-provided uninstall command. Do not delete business data or ad campaigns.
claude mcp remove ryze

Official Documentation & Sources

What it does

A hosted MCP connector for advertising and analytics research with OAuth and approval-gated write actions.

Capability: Search & Web
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Marketing teams analyzing and operating Google Ads, Meta Ads, GA4 and Search Console.

Representative uses

Audit ad accounts
Pull analytics reports
Research keywords/targeting
Create campaigns or creatives with approval

Limitations

Hosted-service dependency.
OAuth scopes and write approval behavior should be checked before production use.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Google/Facebook OAuth
Permissions: Account-scoped advertising and analytics permissions.
Data handling: Queries and operations pass through a hosted connector.
Cost: unknown
Risk and cautions: A hosted connector can read and modify advertising accounts; OAuth scopes and approval controls are material.

Access scope and cautions

Write actions: Campaign, creative and audience writes are described as approval-gated
Sensitive access: Ad accounts Analytics Audiences
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Audit ad accounts; Pull analytics reports; Research keywords/targeting; Create campaigns or creatives with approval.

What setup and authentication are documented?

Recorded installation/entrypoint step: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. Recorded endpoint: https://connector.get-ryze.ai/mcp. Recorded transport: streamable_http. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Google/Facebook OAuth

Can it modify data or perform write operations?

Documented write actions include: Campaign, creative and audience writes are described as approval-gated. Recorded permission boundary: Account-scoped advertising and analytics permissions.

What data-handling boundary should I consider?

Queries and operations pass through a hosted connector. Recorded sensitive-access context: Ad accounts; Analytics; Audiences.

What limitations and risks should I check before use?

A hosted connector can read and modify advertising accounts; OAuth scopes and approval controls are material. Hosted-service dependency. OAuth scopes and write approval behavior should be checked before production use. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

Ryze AI / community repository is listed as Community implementation in MCP100’s current evidence.