Practical overview
When it fits
Use it when an MCP-compatible assistant or automation client needs a hosted connection to advertising or analytics accounts, especially when proposed advertising writes should require approval before application.
Who it is for
- Marketers and agencies working with Google Ads or Meta Ads accounts.
- Teams that want to query advertising, GA4 or Search Console data from an AI client.
- Builders connecting MCP-compatible assistants or automation workflows to these services.
Documented uses
- Review campaign performance and account data through conversational prompts.
- Prepare advertising changes such as budget, bid, campaign or keyword updates for approval.
- Work with keyword research, audiences and creative tasks described in the repository.
- Bring Google Ads, Meta Ads, GA4 and Search Console tools into an MCP-compatible client.
Requirements & limits
The repository describes the MCP connection as free to use and says access is through Google or Facebook OAuth. Account sign-in is part of connecting the relevant services.
- The server is hosted remotely at the endpoint documented in the README; users connect a client rather than installing this server locally.
- The README lists Claude, ChatGPT, Cursor, Windsurf and n8n, with different setup approaches depending on the client.
- Read operations are described as immediate, while advertising writes require approval before application.
- The repository identifies an MIT license and describes more than 250 tools.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect a client to the hosted MCP server
Add the remote connector to a supported client and authorize access to selected advertising or analytics accounts.
Before you start
- A compatible client, such as Claude, ChatGPT, Cursor, Windsurf or n8n.
- A Google or Facebook account associated with the relevant services.
Steps
Add https://connector.get-ryze.ai/mcp as a custom connector in the client, or use the client’s documented MCP server configuration.
Sign in with Google for Google Ads, GA4 and Search Console, or Facebook for Meta Ads.
Select the accounts to connect.
Expected outcome
The client has a configured connection to the selected accounts for the tools exposed by the server.
Guide limitations
- The README describes account access and connection setup, but this guide does not verify a successful connection or any subsequent operation.
- Advertising writes are staged for approval before application.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- irinabuht12-oss/google-ads-meta-ads-mcp · Official homepage title · retained in its source language

