Your accounts. Your permissions.A direct connection to your Google Ads.
Read performance, inspect proposed changes and approve the exact plan. Connect with your own Google account in a compatible MCP client.
This page is public. Google Ads data requires Google authorization. Each user works with the accounts their Google identity can access.
Choose your client.
Gemini web
In Gemini, open Settings → Connected Apps → Add a custom app, paste the endpoint, then follow Google authorization.
Google currently restricts custom apps to adults in the US using a personal Google account, in English, with activity history enabled. Work or school accounts are not eligible according to Google's current guide.
Use @ to select the connected app in your conversation.
Instructions based on Google's documentation. A live Gemini-web connection to this service has not yet been independently verified.
Google's eligibility and setup guide
Gemini CLI
In a local Gemini CLI installation with browser access, add the remote server:
gemini mcp add --transport http mycontent-google-ads https://googleads-mcp.mycontent.academy/mcp
Start Gemini and run:
/mcp auth mycontent-google-ads
Or merge the mcpServers entry from our configuration example into your existing settings. Keep your other servers.
No API keys in this configuration. Authenticate with your own Google account. Compatibility instructions are prepared; live end-to-end Gemini CLI acceptance has not yet been recorded.
Official Gemini CLI instructions
Claude
Open Settings → Connectors → Add custom connector, paste the endpoint and complete Google authorization. A client plan with custom remote connectors is required. This flow has been exercised with the owner's existing connection.
When tools change, disconnect and reconnect the connector to refresh its tool catalogue. A new conversation alone may retain an older catalogue.
A repeatable review, step by step.
- Discover your accounts. Ask the connector to run
list_accessible_customers. Select one account authorized to your Google identity. - Read a report. Request
get_rmf_report with a report code, account and explicit dates. Follow every continuation until has_more=false; one page is not an account total. After a server update, refresh your client's tool catalogue if the report tool is missing. - Inspect a change. Use an authorized test account and request a plan. The plan shows the operations, validation result, warnings and confirmation phrase. Planning does not apply the change.
- Approve the exact plan. After agreeing its scope, provide its returned confirmation phrase to
apply_plan. Sensitive operations require elevated confirmation. - Verify the result. Inspect the apply result, a separate fresh read and
get_audit_log filtered to the selected customer. Do not treat a plan or validation-only result as an applied change.
List my accessible Google Ads accounts.
For my selected account, run get_rmf_report R10 for my chosen date range.
Continue each page until has_more is false, keeping all mandatory columns.
For management review, use only the test account I explicitly select.
Show a validated plan and wait for my approval before any change.
No shared password or operator production-account grant is needed to read your own authorized accounts. If Google's reviewer needs an operator-hosted test environment, arrange a named reviewer and a separate least-privilege grant. That access has not been provided by this public page.
Where the RMF features live.
| Feature | Client tool / location | Review scope |
| R10 / R20 / R40 / R50 / R70 / R100 / R130 | get_rmf_report; additional metric fields via gaql_search and describe_gaql_fields | Fixed mandatory columns and bounded continuation. Refresh an existing client catalogue after a server update. Full client acceptance is recorded separately from query validation. |
| C10 / C20 / C30 / C120 / C190 / C260 / C270 / C300 | plan_generic_mutate, targeting/budget/keyword builders, then apply_plan | Paused Search fixture demonstrated in the owner's account. This is not acceptance of every API parameter. |
| C65 / C75 | Conversion and callout operations through plan_generic_mutate; snippets through gaql_search | Secondary conversion and paused account callout demonstrated. Conversion snippet pairing requires investigation before installation. |
| C96 / C97 / C98; M96 / M97 / M98 | plan_update_bidding_strategy; generic portfolio strategy and campaign operations | Standard and portfolio CPA/ROAS exercises recorded. Warnings and separate readbacks remain part of the evidence. |
| M10 / M110 / M130 / M140 | Settings and status builders; generic campaign, ad and keyword operations | Budget/network edits demonstrated. Disposable campaign/ad/keyword resources completed ENABLED → PAUSED → removal. Existing serving campaigns were not changed. |
Clear boundaries.
Is the service public?
The endpoint and this guide are publicly reachable. Reading or changing Ads accounts requires authorization. Our repository remains private. This guide does not publish account data or the private evidence attachments.
Does this mean Standard Access is approved?
No. The application is under review. Using Gemini does not replace Required Minimum Functionality or Google's access review. Evidence gaps include independent-user acceptance, report acceptance after deployment and applicable campaign-family coverage.
Are the screenshots or examples synthetic?
The private review package identifies its actual own-account captures and any limitations. This public page is a setup guide, not a simulated Ads dashboard or a claim of live test completion.
How do I disconnect?
Remove or disconnect the custom app in your MCP client. To revoke Google authorization, use your Google account's third-party access controls. Client disconnection and Google permission revocation are distinct actions.