You can connect Google Ads to ChatGPT using Google's official, open-source Google Ads MCP server, added in ChatGPT as a custom MCP server (a plugin). It gives ChatGPT read access to your account so you can ask performance questions in plain English. It is a developer-grade setup, not a one-click button, and this guide shows you every step and every limit.
What does connecting Google Ads to ChatGPT actually mean?
Three different things get called "connecting Google Ads to ChatGPT", and they are easy to mix up.
- A live connection to your account. ChatGPT queries your real campaign data through an MCP server. This is what this post covers.
- Prompting workflows. You paste or upload data and use ChatGPT for keyword themes, ad copy and search terms analysis. That is a different job, covered in how to use ChatGPT for Google Ads.
- Advertising on ChatGPT. Buying ad placements inside ChatGPT conversations through OpenAI's Ads Manager. It has nothing to do with your Google Ads account. See our ChatGPT Ads service and the guide on how to advertise on ChatGPT.
The technology behind the first one is the Model Context Protocol (MCP), an open standard that lets an AI model call tools in other systems (modelcontextprotocol.io). What many people still call a ChatGPT connector, OpenAI's current documentation calls a plugin, which can bundle MCP servers and skills (OpenAI plugin docs).
Is there an official Google Ads connector for ChatGPT?
Here is what we could verify on 3 November 2026, and what we could not. OpenAI's plugin documentation names Gmail, Google Drive and Slack as example plugins. It does not name a Google Ads plugin, and the plugin directory at chatgpt.com/plugins sits behind a login, so we could not browse it. Search it for "Google Ads" on your own account first. If an official plugin is listed, install it, read its permissions and skip most of the setup below.
What we could verify is on Google's side. Google publishes an official Google Ads MCP server developer guide and an open-source google-ads-mcp repository. The guide tells you to add a custom connector in ChatGPT or Claude pointing at your deployed server, and it lists the ChatGPT redirect address to allow. That is the route this guide follows.
| Method | Setup effort | Live data | Best for |
|---|---|---|---|
| Plugin from the ChatGPT directory | Low, if one exists. We could not confirm a Google Ads listing | Yes | Anyone, if it is listed on your account |
| Google Ads MCP server added as a custom MCP server | High: Google Cloud project, OAuth client, Cloud Run deployment | Yes, queried on demand | Agencies and in-house teams with developer help |
| Same server run locally with the ChatGPT desktop app or Codex | Medium: runs on your computer, no cloud hosting | Yes, while your computer is on | Technical marketers working solo |
| Export a report, then upload it | Low | No, a snapshot | Everyone else, and one-off analysis |
What you need before you start
- A ChatGPT account (or workspace) where custom MCP servers are allowed. OpenAI says account and workspace policies apply, and Enterprise and Edu workspaces have plugins off by default.
- Access to a Google Ads account, ideally as a read-only user, plus the manager account ID if you work through an MCC.
- A Google Cloud project with billing, because the server needs somewhere to run. Google documents Cloud Run.
- Google Ads API access for that project. Google says developer tokens were sunset on 9 September 2026 and access levels now sit on the Google Cloud project, so you apply for Explorer access instead. Explorer is automated in most cases and allows up to 2,880 operations a day on production accounts (Google access levels).
- Someone comfortable with a command line. You will run gcloud commands and set environment variables.
How to connect Google Ads to ChatGPT, step by step
These steps follow Google's server guide and OpenAI's instructions for adding a custom MCP server. Menu labels are quoted from OpenAI's documentation, and OpenAI changes these screens often, so expect small differences.
-
1
Check your plan, workspace permissions and the plugin directory
Open chatgpt.com/plugins on your ChatGPT account and search for Google Ads. If an official plugin is listed, install it and review its permissions. If not, confirm you are offered the plus button and Add custom MCP server. In a managed workspace, ask your admin to allow plugins and custom MCP servers.
-
2
Create a Google Cloud project and enable the Google Ads API
In the Google Cloud console, create or pick a project and enable the Google Ads API, which grants Test access. Then apply for Explorer access on the Google Ads API Overview page so the project can read production accounts, up to 2,880 operations a day.
-
3
Create a Google OAuth client for the server
Create an OAuth 2.0 Web application client. Add https://chatgpt.com/connector_platform_oauth_redirect as an authorised redirect URI, add the https://www.googleapis.com/auth/adwords scope to the OAuth consent screen, and, if the consent screen is in Testing, add the Google accounts that will connect as test users.
-
4
Deploy the Google Ads MCP server
Build the server image from the googleads/google-ads-mcp repository with Cloud Build, then deploy it to Cloud Run with your project ID, OAuth client ID and secret and FASTMCP_HOST set to 0.0.0.0. After the first deploy, set GOOGLE_ADS_MCP_BASE_URL to the Cloud Run address. Never deploy it publicly without the OAuth client ID and secret set.
-
5
Add the server to ChatGPT as a custom MCP server
At chatgpt.com/plugins select the plus button, then Add custom MCP server. Enter a name and description, enter your Cloud Run address ending in /mcp as the connection, choose OAuth 2.0 and enter your OAuth client ID and secret. Review the risk warning, select I understand and want to continue, then select Create as a plugin.
-
6
Sign in with Google and grant read access
Install the new plugin and connect it. Sign in with a Google user that has access to the Google Ads account, ideally read-only access, and approve the Google Ads scope. If you reach clients through a manager account, supply its customer ID as the login customer ID.
-
7
Test the connection in a new conversation
Start a new conversation, type the at symbol and choose your plugin, then ask what customers you have access to. You should see the account IDs and names you can reach. If tools are missing, open the connection in chatgpt.com/plugins and select Refresh.
-
8
Ask a real question and check the answer against Google Ads
Ask for something specific, such as the top spending campaigns by device over the last 7 days, then open the same report in the Google Ads interface and compare the figures before you act on any of it.
Google's guide carries one warning worth repeating. For ChatGPT to reach the server, Cloud Run is deployed with unauthenticated access allowed, and the server then enforces Google sign-in itself. If you leave out the OAuth client ID and secret, it falls back to the container's own credentials and exposes them to anyone who finds the address. Always set both. The steps and settings are in OpenAI's connect and test guide and Google's developer guide.
What can you ask ChatGPT once Google Ads is connected?
Under the hood, ChatGPT turns your question into a Google Ads Query Language (GAQL) request and runs it with the server's search tool. Google's own sample prompts include "How many active campaigns do I have?" and "Give me a report of the top spending campaigns split by device category over the last 7 days for account 1234567890." Here are prompts in the same spirit for Australian advertisers:
- Performance: "Compare clicks, cost and conversions by campaign for the last 30 days against the previous 30 days, and flag anything that moved by more than 20 percent."
- Search terms: "List search terms from the last 14 days that spent more than $50 AUD with no conversions, and suggest which to review as negative keywords."
- Budget pacing: "Show each campaign's daily budget next to average daily spend this month and tell me which are capped or underspending."
- Structure: "Which campaigns are enabled but have had no impressions in the last 7 days?"
One practical trap: the Google Ads API reports money in micros, where 1,000,000 micros equals one unit of your account currency. A good prompt asks ChatGPT to convert to dollars and state the account currency and date range it used. Then check the figures in Google Ads before anyone makes a decision, because the model can write a wrong query and still sound sure.
What can the connection not do?
Mostly, it reads. Google's guide calls the server strictly read-only and says it cannot modify bids, pause campaigns or create assets. The open-source README lists a few extra tools for assets and labels with a propose and confirm step, and the guide and README disagree on this, so check the version you deploy. None of the listed tools change bids, budgets or campaign status.
| Task | Google Ads MCP server |
|---|---|
| List the accounts you can access | Yes, with the list accessible customers tool |
| Query campaigns, budgets, status and metrics | Yes, through the search tool using GAQL |
| Look up which fields and metrics exist | Yes, through the resource metadata tool |
| Change bids or budgets, or pause campaigns | No tool for this |
| Create assets or manage labels | Guide says no. README lists limited tools with propose and confirm. Verify your version |
| Replace judgement on strategy | No. It reports, you decide |
The honest summary: it is a fast way to ask questions of your data, not an autopilot. For the optimisation work itself, our guide on using ChatGPT for Google Ads covers where ChatGPT helps and where a human should stay in the loop.
Privacy and account access for Australian businesses
Connecting an AI model to an ad account moves data. Google's README states plainly that the MCP server will expose your data to the agent or model you connect to it, and OpenAI's documentation adds that when ChatGPT sends data through an MCP server, that service's terms and privacy policy apply. Four habits keep this sensible:
- Least access. Every request runs as the Google user who signed in, so connect with a read-only Google Ads user rather than an administrator. This is our recommendation, built on how Google describes the server's identity model.
- Mind the search terms report. Real people type real queries, and some contain personal details. If your business is covered by the Privacy Act 1988, treat that data as personal information. The OAIC publishes guidance on privacy and commercially available AI products worth reading first.
- Client permission. If you are an agency, get written approval before connecting a client's account. Their data, their decision.
- Lock the server down. Keep the OAuth client secret out of chat and out of shared documents, and restrict who can sign in to the server through your OAuth test users or consent screen settings.
Troubleshooting: when it will not connect
- No Add custom MCP server option. Your plan or workspace policy may not allow it. Ask your admin, or check chatgpt.com/plugins on a different account.
- Redirect or sign-in errors. Confirm https://chatgpt.com/connector_platform_oauth_redirect is on your OAuth client, the adwords scope is on the consent screen, and the signing-in user is a test user if the app is in Testing.
- A 401 response. Google notes that clients without OAuth support get HTTP 401 from the hosted server. ChatGPT supports OAuth, so check that your client ID and secret match on both sides.
- An error saying access is limited to test accounts. Your Google Cloud project only has Test access. Apply for Explorer access on the Google Ads API Overview page.
- Permission errors on client accounts. Supply the manager account ID as the login customer ID.
- Tools missing or out of date. Open the connection in chatgpt.com/plugins, select Refresh, then start a new conversation.
No supported plan, or no developer? Alternatives that work today
You do not need a live connection to get value. Download a search terms or campaign report from Google Ads as a CSV, upload it to ChatGPT and ask the same questions, which is the workflow in our ChatGPT for Google Ads guide. You can also have a Google Ads script or scheduled export write to a Google Sheet and use OpenAI's Google Drive plugin, which OpenAI lists for working across Drive, Docs and Sheets. The data is a snapshot rather than live, but the setup takes minutes.
If you would rather have the numbers read by someone who runs Australian accounts daily, that is what our Google Ads campaign management team does, with AI used where it saves time and humans where it matters. And if your real question is where to spend next, see how the two channels compare in ChatGPT Ads vs Google Ads.
In short
How do you connect Google Ads to ChatGPT?
Key takeaways
- The verified route is Google's official Google Ads MCP server added to ChatGPT as a custom MCP server. We could not confirm a one-click Google Ads plugin, so check chatgpt.com/plugins on your account first.
- Setup needs a Google Cloud project, Google Ads API access (Explorer allows up to 2,880 operations a day on production accounts), a Google OAuth client and a Cloud Run deployment.
- Once connected, ChatGPT can query campaigns, budgets, status and metrics, including search terms and budget pacing. Google calls the server strictly read-only, so it does not change bids, budgets or campaign status.
- Connect with a read-only Google Ads user, protect the OAuth secret, and get client permission first. Search terms can contain personal information under the Privacy Act.
- Connecting Google Ads to ChatGPT is different from prompting workflows and different from advertising on ChatGPT.