Connect Google Ads to ChatGPT or Claude: prove the first read
To connect Google Ads to ChatGPT or Claude, use an available MCP server with Google authorization and a transport your client supports. Confirm the account and a small reporting query before relying on its answers. In Variafy, Google Ads is read-only: its own reports and checks, available after your beta invitation.
On this page9 sections
What connects the assistant to Google Ads?
An MCP server runs the Google Ads requests and returns data to the assistant. Google’s MCP integration guide, checked 19 Oct 2026, documents an official implementation with account discovery, reporting queries and resource metadata.
Mode: Read-only (current release)
| Documented connection route | What your operator must provide | |
|---|---|---|
| Local server | Google supports standard input/output, or stdio. | A locally configured server and credentials in a client that supports that mechanism. A launch command is not a URL to paste into a web connector. |
| Remote server | Google also documents Streamable HTTP and Cloud Run hosting. | A reachable MCP endpoint with the required authentication and client callback configuration. Deployment is work for the integration owner. |
Our suggestion is to ask the integration owner for the exact endpoint or local setup, server owner, supported reads and intended Google account before starting. Do not infer that a publicly documented server is already hosted for your business; the same guide distinguishes deployment from an allowlisted hosted-endpoint pilot.
A useful first task for a lead business is a small, clearly scoped performance report. Use the Google Ads reporting guide to decide which conversion result you actually want explained.
Does “read-only” describe the Google permission or the tools?
For Google’s current MCP implementation, read-only describes the tools, not a separate Google permission. Check Google access, server capabilities and client permissions separately. Google’s access-model documentation says the API uses the same OAuth scopes for read-only and read-write operations; it follows Google Ads user roles.
| What the document establishes | Our check before use | |
|---|---|---|
| Google authorization | Account roles apply through direct access or a manager hierarchy; the login-customer-id can resolve the access path. | Name the authorized identity and intended advertiser account. Ask the owner to confirm the effective role and manager path. |
| MCP server | Google’s current documented implementation cannot modify bids, pause campaigns or create assets. | Inspect the actual server and exposed tools. A different implementation may have a different boundary. |
| AI client | OpenAI and Anthropic document tool controls and authentication for custom MCP connections. | Keep the first task to necessary reads, inspect what is requested, and avoid treating a remembered approval as a server-side restriction. |
OpenAI’s custom-MCP documentation warns that an untrusted server may access information or trick ChatGPT into using tools in unintended ways. Anthropic’s connector guidance likewise describes the server as an intermediary with access under the granted permissions. Our reading: reading can still disclose account data.
There is also a dated setup change: Google’s current MCP guide says developer tokens were sunset on 9 September 2026; its latest setup uses Google Cloud project access and OAuth credentials. Have the operator follow that current guide rather than copy an older token checklist.
How do you add a remote Google Ads MCP server in ChatGPT?
For an available remote server, use ChatGPT’s custom MCP connection flow and then authenticate as required by that server. As of 19 Oct 2026, the official OpenAI instructions describe ChatGPT on the web, subject to workspace permissions and security restrictions.
- Open ChatGPT Plugins. Select the plus button, then Add custom MCP server.
- Identify the server. Enter its name and, under Connection, its Server URL. Use the actual server operator’s endpoint.
- Configure authentication. Follow the server’s documented OAuth requirements and examine the permissions and risk warning before accepting.
- Create and install the plugin. The documented action is Create as a plugin; install the resulting plugin before using it in a conversation.
- Select it in the conversation. Type @, choose the installed plugin and ask for the first scoped read.
OpenAI documents SSE and streaming HTTP support here. Google’s remote route uses Streamable HTTP; its local stdio command is a different setup. If the server or workspace is unavailable, resolve that prerequisite with its owner instead of treating an ordinary chat as an account connection.
How do you add a remote Google Ads MCP server in Claude?
Use Claude’s custom remote connector flow for a hosted MCP endpoint; local desktop configuration is a separate mechanism. The Anthropic instructions, checked 19 Oct 2026, list custom remote connectors on Free, Pro, Max, Team and Enterprise; Free users are limited to one custom connector.
The following individual steps are documented for Pro and Max, with separate organization steps for Team and Enterprise. The page gives no separate Free procedure, so this guide does not assume Free follows the Pro/Max steps.
- Open Customize → Connectors. Select + Add → Add custom connector.
- Enter the name and remote MCP server URL. Select Continue.
- Check the detected authentication. Use the sign-in and OAuth-client choice required by the actual server; an operator may need to configure callbacks.
- Finish with Add and authenticate. In a Team or Enterprise workspace only certain roles can add the connector: Owners and Primary Owners on Team; Owners, Primary Owners and people with a custom role that includes Manage access to Libraries on Enterprise. Members then connect individually.
- Enable it for the conversation. Use the conversation’s connector controls and ask for the initial read.
Google’s Cloud Run setup says to use your own OAuth Client ID and Client secret
, while Anthropic labels Use Claude’s published identity (Recommended)
as its recommended OAuth-client choice.
Our reading: these instructions differ; confirm the client configuration required by the actual server rather than choosing from the label alone.
The Google server requests the https://www.googleapis.com/auth/adwords scope. That is the shared API scope described in the access model, not a separate read-only permission.
Anthropic says a remote connector connects from its cloud infrastructure, including when used in Claude Desktop. A private URL reachable only from your laptop is therefore not proof that this remote route can reach it. Use the documented network requirements with the operator.
These are dated client instructions, not an assurance of access for every account or plan. Confirm the workspace’s available connector controls before arranging a production reporting workflow.
What should the first Google Ads read prove?
It should establish the intended advertiser account and a report you can reconcile on the same basis. Our suggested acceptance task is deliberately small: account identity, followed by campaign performance for one closed reporting period.
First-read prompt
“Use only the connected Google Ads reporting tools. Identify the intended advertiser account and state its currency and time zone. For the exact dates I specify, show campaign spend and the named conversion metric. State filters, row limits and whether the returned data is complete. Do not change anything.”
| Acceptance evidence | If it does not match | |
|---|---|---|
| Account | The intended advertiser ID, not just a manager name. | Check the authorized identity and hierarchy. Google’s access model says ListAccessibleCustomers lists direct access; a manager’s client accounts may require hierarchy traversal. |
| Reporting basis | Exact dates, time zone, currency, conversion definition and filters. | Reconcile on the same basis in the reporting source before discussing improvement. A different conversion definition is a different question. |
| Coverage | The report states pagination, filters and missing fields where the implementation exposes them. | Narrow the request or obtain the missing data. Do not label a partial row sum the account total. |
Save this small accepted report as a reference for the team, with its query basis and date. A fluent explanation is not a substitute for matching evidence. The Google Ads audit checklist helps choose the next business question after the connection has passed this check.
Search-term reporting and CRM outcomes have their own coverage and definitions: use the search terms guide and offline-conversion guide rather than assuming one connection makes every lead a confirmed sale.
What is the Google Ads status in Variafy?
Variafy reads Google Ads to build its own reports, checks and alerts after your beta invitation. It does not change Google Ads and does not pass the Google Ads API through to other programs.
Variafy reads account identity, campaign settings and campaign performance. The performance read records the reporting period and account currency and flags incomplete coverage; its totals cover only the rows returned.
Google Ads works right after your beta invitation. These tools read data and do not change Google Ads.
A useful connection handover
Our suggestion: for any tool you connect, write down the intended account, one reporting question and the acceptance checklist above before looking at an answer. Do not connect a live account to a tool until its owner confirms what it reads.
Join the free beta for Variafy. Keep account changes with the responsible human; this guide’s product workflow is reading and a proposed investigation.
What should you hand over if the connection fails?
Record which stage failed, the expected account and the non-secret evidence the operator needs. Our suggested handover separates reachability, authentication, authorization and reporting, so “it does not work” becomes a specific task.
- Server discovery. Confirm the correct endpoint and transport with its owner; distinguish a local launch configuration from a hosted connector.
- Authentication. Note whether the client reached the server and offered the expected sign-in. Google’s guide says clients without its HTTP OAuth support receive a 401 response; that is different from an empty report.
- Account authorization. Identify the target advertiser and manager route. Ask the access owner to verify the effective Google role.
- Report reconciliation. Attach the account, period, metric definition, filters and coverage statement. Keep passwords, tokens and credential files out of the chat.
Use a launch-readiness checklist with named owners: server operator, Google access owner and person accepting the report. The connection is useful when those people can explain what data was read and what remains unknown.
How we checked
Checked on 19 Oct 2026 against 4 public documents: Google’s Ads MCP integration guide (last updated 16 Oct 2026) and Google Ads access model (last updated 14 Oct 2026);
OpenAI’s Add custom MCP server guide and Anthropic’s custom remote MCP connector guide.
Questions
Can I connect Google Ads to ChatGPT or Claude?
Yes, through an available MCP server and a compatible client connection, with the required Google access. Google documents local and remote MCP routes; client permissions and server availability still need checking.
Is Google’s official Google Ads MCP server read-only?
Google describes its current implementation as strictly read-only: it retrieves data and cannot modify bids, pause campaigns or create assets. That statement applies to the documented implementation, not every MCP server.
Does Google Ads have a read-only OAuth scope?
Google’s access-model documentation says read-only and read-write operations use the same OAuth scopes. Effective Google roles, the server’s implemented tools and the assistant’s permissions are separate controls.
Can I paste a local MCP command into ChatGPT?
A local stdio launch command is not a remote MCP server URL. Use a connection mechanism supported by your client and the server; have the operator provide the correct route.
Why can the connector see a manager but not my advertiser account?
Google documents that ListAccessibleCustomers returns directly accessible accounts. Access to an advertiser through a manager may require inspecting that manager hierarchy and using the correct login-customer-id; it is not proof that the advertiser account is absent.
Can I connect production Google Ads through Variafy now?
After your beta invitation, you can connect Google Ads for reading and analysis. The tools do not change Google Ads.