Google Ads MCP for Claude and ChatGPT, without a Google Cloud project

Google’s MCP server page, last updated October 16, 2026, says developer tokens “were sunset on September 9, 2026, and are no longer required in the latest version of the Google Ads MCP server.” Its deprecations page says the same. If an older setup still sends a token, the API ignores it, and Google says it will start rejecting tokens in a future major version of the API.

Google publishes the server in its developer toolkit. Here’s what it needs instead of a token:

1. Your own Google Cloud project, approved for real accounts. When you turn on the Google Ads API, a new project starts at Test access, which, in Google’s words, “can only make Google Ads API requests against test accounts.” Until you apply for Explorer access or higher in Cloud Console and get it, every question about a real client account fails with an error such as CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION (that’s the wording in API version 25; older versions return ACTION_NOT_PERMITTED).
2. OAuth credentials. A client ID and secret from your Cloud project, or application default credentials. Signing in asks for the Google Ads scope (adwords).
3. Python. The server is a Python program. You run it on your computer with pipx, and an AI tool on the same computer, such as Claude Code, talks to it there.
4. Your own Cloud Run deploy, for Claude on the web or ChatGPT. Neither can launch a program on your laptop. Google’s page shows how to deploy the server to Google Cloud Run and add your Cloud Run URL, ending in /mcp, as a custom connector with your own OAuth client ID and secret.

Google’s access levels page says Explorer reaches real accounts, with a daily limit:

Google counts a day as a rolling 24 hours, and it doesn’t say how many operations one chat question uses. New applications for Basic or Standard access also need brand verification of your Cloud project first.

If you already work in Google Cloud, all of this is a checklist. If you report on client Google Ads accounts and Cloud Console is new to you, it’s a real chore, and you have to finish it before you can ask a single question. We don’t think asking what a client spent yesterday should need a Cloud project. With SyncWith, it doesn’t.

Here’s the whole setup with SyncWith:

1. Add the server to your assistant. Paste this URL into Claude or ChatGPT as a custom connector:

   https://mcp.syncwith.com/mcp

   Every Claude plan can add one, though Free allows a single custom connector. In ChatGPT, an admin of a Business, Enterprise or Edu workspace adds it, and Pro users can connect it with read and fetch permissions only. Step by step: Claude, ChatGPT.

2. Sign in with Google. No SyncWith account? We create a free one for you. If you already use SyncWith, use the same Google account.
3. Ask your assistant to connect Google Ads. It replies with a link to a Google sign-in screen. Sign in to the Google account that can see your clients’ Google Ads accounts, then come back to the chat.

That’s it. No developer token, no Cloud project, nothing to install.

When you ask a question, SyncWith calls Google Ads’ own API at that moment and hands the rows back to your assistant. It only reads: it never changes your campaigns, orders, reports or databases.

Google’s server reads Google Ads only. SyncWith’s MCP server lets Claude query Google Ads and GA4 data in the same chat, along with Facebook Ads, Shopify and 15 more sources. Put a client’s Google Ads cost next to the conversions GA4 recorded for the same days, without a second tool.

There’s no separate charge for the MCP server today. Each live query uses one refresh from your SyncWith plan, the same as refreshing a report, and the free Hobby plan includes 35 refreshes a month. Listing your sources and fields doesn’t use any.

Start each question with “Using SyncWith,” so your assistant answers from SyncWith and not from another tool you’ve connected.

1. “Using SyncWith, list my Google Ads accounts.”

   Your connection test. If your client accounts come back by name, the setup worked, and you have the exact names to use in every question after this one.

2. “Using SyncWith, show spend, clicks and conversions by campaign for the [client account name] account over the last 30 days. Use the client account, not the manager account.”

   Google Ads only returns metrics for client accounts. Ask for a manager account’s metrics and the API refuses with REQUESTED_METRICS_FOR_MANAGER. So name one client account per question, whichever server you use.

3. “Using SyncWith, show yesterday’s spend, clicks and conversions for the [client account name] account, in the account’s own time zone.”

   Google dates every number in the account’s own time zone, not yours. Conversions can land hours after the click, so yesterday’s conversions can still go up after you ask. And “last 7 days” in Google Ads leaves out today.

If a client report needs every account under a manager account in one place, that’s a job for our Google Ads to Google Sheets integration: pick the manager account and it pulls every client account under it, in one report or separate ones, on a schedule you set.

Does Google have an MCP server for Google Ads?

Yes. Google has published an official, open-source MCP server for the Google Ads API since October 2025. It has three tools: one lists the accounts you can reach, one runs Google Ads Query Language (GAQL) searches, and one looks up the fields a resource has.

What is the Google Ads MCP server URL?

Google’s page doesn’t list a public one: the URL is wherever you run its server. SyncWith’s is https://mcp.syncwith.com/mcp.

Can an MCP server change my Google Ads campaigns?

Google’s current release can’t. Its page says it “cannot modify bids, pause campaigns, or create new assets.” SyncWith’s never changes your campaigns either. Some third-party servers can make changes, so check what a server can do before you connect a client’s account.

More on tools, data and plans is in the SyncWith MCP docs.