Connect RIPGestor to your MCP client

The authorization starts inside a compatible MCP client and continues in your default browser.

No Google password is entered into RIPGestor. Authentication and consent happen on Google-controlled pages. The MCP client receives a RIPGestor session, not your Google password or browser cookies.

Connection flow

  1. Add the RIPGestor remote MCP serverUse the server address supplied by MARTIS TECH in Claude, Codex or another compatible client.
  2. Choose Connect or AuthenticateThe client opens the RIPGestor consent screen and then redirects to Google in your external browser.
  3. Review the requested permissionsChoose the Google account and approve only the access needed for the advertised Google Ads features.
  4. Return to the MCP clientThe client must show the server as connected. A read-only account discovery request is the final connection check.

What is available after authorization

The MCP can expose account discovery, performance reporting, keyword planning, approved campaign operations and consent-based website measurement. Availability depends on the connected account, its Google Ads role, the developer-token access level and Google product eligibility.

Disconnect and delete

You can revoke the Google grant from your Google Account, disconnect the server from your MCP client and request deletion of Martis-held data. See the Data Deletion page for the complete procedure.

Need help?

Use the support form and select “Google Ads or RIPGestor access”. Do not send passwords, refresh tokens, developer tokens or client secrets.