Back to blog
Article

How to Connect Google Ads to Claude with an MCP Server

Updated November 7, 2026
18 min read
By InsightfulPipe
On this page
How to Connect Google Ads to Claude with an MCP Server

InsightfulPipe publishes this guide. It describes Google's official server first, then gives the steps for InsightfulPipe's hosted Google Ads MCP server.

Last updated: 2026-11-02

Short answer: You can connect Google Ads to Claude with an MCP server in two ways. Google's official google-ads-mcp server reads reports but cannot pause campaigns or change budgets, and you host it yourself with a Google Cloud project, an API access level and OAuth credentials. InsightfulPipe's hosted Google Ads MCP server takes one URL: connect Google Ads in InsightfulPipe, add https://google-ads.insightfulmcp.com/ as a custom connector in Claude, and click Authorize access. Plans start from $29.99 a month.

How to connect Google Ads to Claude with an MCP server

Two routes work today. They differ in who runs the server and whether Claude can change anything. Both let Claude call Google Ads tools over the Model Context Protocol (MCP).

With Google's official server (no campaign or budget changes, you host it):

  1. In a Google Cloud project, enable the Google Ads API and get Explorer, Basic or Standard access.
  2. Create an OAuth client, or sign in with Application Default Credentials and the adwords scope.
  3. Install pipx and add the server to Claude Desktop or Claude Code.
  4. For claude.ai on the web, deploy it to Cloud Run with your own OAuth client first.

With InsightfulPipe (hosted, reads and writes):

  1. In InsightfulPipe, open Connected accounts, click Connect account and choose Google Ads.
  2. Pick Read-only or Read & write, click Continue with Google Ads and select your accounts.
  3. In Claude, open Customize > Connectors, click + Add, then Add custom connector.
  4. Name it Google Ads, paste https://google-ads.insightfulmcp.com/, click Continue twice, then Add.
  5. Click Connect, sign in to InsightfulPipe if asked, and click Authorize access.
  6. In a new chat, click +, open Connectors and switch Google Ads on.

InsightfulPipe

Google's official server

Setup

Sign in with Google, paste one URL

A Cloud project, an API access level and OAuth credentials

Hosting

Hosted, nothing to install

Your computer through pipx, or Cloud Run you deploy

Google Ads actions

108: 39 read, 65 write, 4 destructive

7 tools: 3 read, 4 that create assets or manage labels

Changes campaigns

Yes, within switches an admin sets per account

No: no pausing, budgets, bids or new campaigns

In claude.ai

Paste the URL under Customize > Connectors

After a Cloud Run deploy with your own OAuth client

Price

From $29.99 a month

Open source (Apache-2.0), self-hosted

Other platforms

49 more platforms, including Meta Ads and GA4

Google Ads only

The InsightfulPipe action control for one Google Ads account: 104 of 108 actions on, with read only 39 of 39, write 65 of 65 and destructive 0 of 4.

Watch: Connect Google Ads to Claude AI, a report and a new campaign from one prompt (2 min 34 s)

The video may show earlier setup screens. Follow the steps in this article for the current route.

Google's official Google Ads MCP server, step by step

Google's Ads API team publishes google-ads-mcp, an open-source Python server under Apache-2.0. Its guide, last updated 2026-10-30, lists the mode as "Read-only (current release)" and says it "cannot modify bids, pause campaigns, or create new assets". It lists accounts and runs GAQL reports. Its v0.0.6 release of 2026-11-02 adds four write tools for assets and labels, each behind a propose-and-confirm step. It still cannot pause campaigns, change budgets or bids, or create campaigns. You run it yourself.

Google's Google Ads MCP server guide: Mode read-only in the current release, and a prerequisites note that developer tokens were sunset on September 9, 2026.

What it needs:

  • A Google Cloud project with the Google Ads API on. Enabling the API gives Test access, which reaches test accounts only. Real accounts need Explorer, Basic or Standard access, which you apply for on the API overview page.
  • Credentials. An OAuth client ID and secret, or Application Default Credentials from gcloud auth application-default login with the adwords scope.
  • pipx on the computer that runs Claude Desktop or Claude Code.
  • No developer token. Google sunset developer tokens on September 9, 2026, and its guide says the latest server needs none. The README still marks a token step "Optional" and shows the variable in its examples.

Claude Code. One command registers the local server:

claude mcp add google-ads-mcp --env GOOGLE_PROJECT_ID=YOUR_PROJECT_ID --env GOOGLE_APPLICATION_CREDENTIALS=/path/to/credentials.json -- pipx run --spec git+https://github.com/googleads/google-ads-mcp.git google-ads-mcp

Claude Desktop. Add Google's mcpServers block, with the same two variables, to claude_desktop_config.json, then restart the app. Anthropic notes that servers configured in that file are not available in claude.ai or Cowork.

claude.ai on the web. Google's guide has you host the server first:

  1. Build the image with Cloud Build into an Artifact Registry repository.
  2. Create a Web application OAuth client with the adwords scope and Claude's redirect URI, https://claude.ai/api/mcp/auth_callback.
  3. Run gcloud run deploy with that client, then add the Cloud Run URL, ending in /mcp, as a custom connector with your own OAuth client.

Google's own hosted endpoint is a pilot for allowlisted participants, and the latest release is v0.0.6, from November 2, 2026 (releases). Google's token page lists two known issues: some projects whose Cloud billing is still on the trial program are refused Explorer or Basic access, and some projects upgraded after September 9 get AUTHORIZATION_ERROR on production accounts.

So the official server needs a Cloud project, credentials and a machine or Cloud Run service you maintain. Its three read tools, list_accessible_customers, search and get_resource_metadata, include no Keyword Planner, and its four write tools reach only assets and labels.

What you are actually connecting

With InsightfulPipe, you connect Claude to a hosted Google Ads server, and that server to the Google Ads accounts you authorize. The whole path fits on one line:

Claude → InsightfulPipe Google Ads MCP server → your authorized Google Ads accounts

Claude never sees your Google password. It sends a request over MCP, and InsightfulPipe runs the matching Google Ads API call with the OAuth access you granted. Reports run as read-only GAQL queries through query_data, and changes go through a separate tool, execute_action. That split is how MCP differs from calling the API directly. You need no developer token, Cloud project or server to host.

Before you start

You need four things before you start, and none of them is a developer token, a Cloud project or code.

  • Google Ads access. A Google login that can open the account, or the manager (MCC) account above it.
  • An InsightfulPipe workspace. Plans start from $29.99 a month, and each Google Ads account counts as one of Starter's 8 connections. Start a trial.
  • A role that can connect. Owners, Administrators and Operators connect accounts and set their actions. See workspace roles and permissions.
  • A Claude plan with custom connectors. Free, Pro, Max, Ultra, Team and Enterprise include them, and Free allows one (Anthropic, checked 2026-11-01).

Google's own access levels still apply. Read-only can view campaigns and run reports but cannot edit campaigns; Standard and Admin can. InsightfulPipe cannot expand the authority of the Google login you connect.

Step 1: Connect Google Ads in InsightfulPipe

Step 1 links your Google Ads accounts to your InsightfulPipe workspace. You choose how far the assistant may go before you sign in with Google.

  1. Open Connected accounts and click Connect account.
  2. In Add an integration, find Google Ads and click Connect.
  3. Choose Read-only or Read & write. The Agent actions list underneath shows what each allows.
  4. Click Continue with Google Ads.
  5. Sign in with Google and approve access.
  6. Select the accounts to connect, including client accounts under a manager.
Step 1 of 3 in InsightfulPipe: the Add an integration grid, with the Google Ads card and its Connect button.Step 2 of 3 for a Google Ads connection: Read-only or Read & write, every action listed with its switch, and destructive actions at 0 of 4 before any sign-in.

Each account becomes its own connection with its own switches. Google Ads uses one OAuth scope for reading and changing, so InsightfulPipe enforces Read-only on its own server: a Read-only connection locks every write until an admin reconnects it with Read & write.

For a manager account, pick client accounts from the list. Each is stored with its manager, so requests carry the right login-customer-id header. The Google Ads connector reference lists every action. Agencies with many clients can follow our Google Ads MCP guide for agencies.

Step 2: Add the connector URL in Claude

Step 2 adds the Google Ads server to Claude as a custom connector. The same steps work in claude.ai and Claude Desktop.

  1. Copy the server URL, https://google-ads.insightfulmcp.com/.
  2. In Claude, open Customize > Connectors.
  3. Click + Add, then Add custom connector.
  4. Name it Google Ads, paste the URL and click Continue.
  5. Keep the sign-in settings Claude detects, click Continue, then Add.
  6. Click Connect, sign in to InsightfulPipe if asked, and click Authorize access.
The Google Ads MCP page inside InsightfulPipe: the server URL, the Open Claude Directory button and the client tabs.Claude's Add custom connector dialog with the name Google Ads and https://google-ads.insightfulmcp.com/ filled in, and the Continue button highlighted.

After the InsightfulPipe sign-in, a Grant access to Claude page lists your accounts by brand and the requested permissions. Click Authorize access. Claude reaches only the Google Ads accounts your workspace connected and granted to you. With no Google Ads account connected yet, the page says "You can still authorize now", and tools that need an account ask for one.

On Team and Enterprise plans, an Owner first adds the connector under Organization settings > Connectors, and each member clicks Connect. To connect every platform at once, click Open Claude Directory in the app for the full InsightfulPipe MCP server.

Step 3: Turn the connector on in a new chat

Claude switches connectors on per conversation, so turn Google Ads on in each chat.

  1. Start a new chat.
  2. Click + at the lower left.
  3. Open Connectors and switch Google Ads on.
A new Claude chat with the + menu open on Connectors and the Google Ads connector switched on.

Claude adds its own approval layer. Open the connector under Customize > Connectors and set each tool to Always allow, Needs approval or Blocked (Anthropic, checked 2026-11-01). Allow query_data and set execute_action to Needs approval.

Step 4: Choose which actions the assistant may run

Step 4 decides, account by account, which of the 108 Google Ads actions the assistant can use. A new Read & write connection starts with 104 of 108 on: every read and write action, with the 4 destructive actions off.

  1. In InsightfulPipe, open Connected accounts.
  2. On the account's row, click the actions button, such as 104/108 actions.
  3. Use the All, Read only, Write and Destructive tabs to switch actions on or off.
  4. Click Save actions.

Only an owner, admin or operator can change these switches. The server refuses a switched-off action in every AI client and tells the assistant: "This action is disabled for this connected account. An owner or admin must enable it for the account."

The Destructive tab for a Google Ads account in InsightfulPipe: the four remove actions switched off, the default until an admin switches them on.

Step 5 (optional): Connect Google Ads to Claude Code

Claude Code takes one command and one sign-in, and the same account switches apply as in claude.ai.

claude mcp add --transport http google-ads-mcp https://google-ads.insightfulmcp.com/
  1. Run the command in your terminal.
  2. Start Claude Code, run /mcp, select google-ads-mcp and choose Authenticate.
  3. Sign in to InsightfulPipe if asked, then click Authorize access.

claude mcp login google-ads-mcp runs the same sign-in from your shell. Local scope, the default, covers the current project, and --scope user covers every project (Claude Code docs, checked 2026-11-01). For scripted reports, the InsightfulPipe agentic CLI reaches the same accounts from the terminal.

Other clients: ChatGPT, Cursor, Gemini CLI and Codex CLI

The same URL works in any client that supports remote MCP servers, with the same InsightfulPipe sign-in, Authorize access and account switches.

ChatGPT. Go to Plugins, click Add, choose Add custom MCP server, paste the URL, keep OAuth, tick I understand and want to continue and click Create as a plugin. The Google Ads MCP server for ChatGPT guide also covers the one-click directory install.

Cursor. Use the install link in the setup section of the Google Ads MCP page, or add the URL to ~/.cursor/mcp.json. At Needs authentication, click Connect, sign in if asked, and click Authorize access.

Gemini CLI and Codex CLI. One line each:

gemini mcp add --transport http google-ads-mcp https://google-ads.insightfulmcp.com/
codex mcp add google-ads-mcp --url https://google-ads.insightfulmcp.com/

In Gemini CLI, run /mcp auth google-ads-mcp. If Codex CLI opens no browser, run codex mcp login google-ads-mcp.

Verify it worked

Three checks, shortest first, confirm the connection without changing anything in your account.

1. The connection is live. In a new Claude chat, open +, then Connectors, and find Google Ads switched on. In Claude Code, claude mcp list shows google-ads-mcp as ✔ Connected, or ! Needs authentication until you finish /mcp.

2. A prompt that cannot do harm. Paste this as it is:

List the Google Ads accounts available to this connection.
Return the account name, customer ID, currency, and status.
Do not run a report and do not change anything.

3. A real read. Ask for last week's cost by campaign and compare one number with Google Ads. If they disagree, check the date range and the account's time zone.

Prompts to run first

Start with reads that answer a real question, then one change that stays paused. Search term questions run search_terms_report, keyword ideas run generate_keyword_ideas, and a new Search campaign runs create_search_campaign, which always creates it paused. Name the account first: each request works on one account.

Two prompts to paste as they are:

Use Google Ads account [CUSTOMER_ID].

Compare the last 30 complete days with the previous 30 complete days.
Break the report down by campaign.
Include cost, impressions, clicks, conversions, cost per conversion and conversion value.
Use Google Ads account [CUSTOMER_ID].

List every search term from the last 14 days with more than [SPEND] in cost and zero conversions.
Group them by campaign and ad group.
Propose them as negative keywords, but do not add anything yet.
Example data: the answer to the 30 day comparison prompt, with cost, impressions, clicks, conversions, cost per conversion and conversion value for each Google Ads campaign and the change against the previous 30 days.

The prompt library, the 50 Google Ads prompts for Claude and the Google Ads Claude skills are free to use. Claude skills package a whole job: the search term audit skill runs the second prompt in one go. For the full set, see the best Claude skills for Google Ads.

What the assistant may change, and who decides

The assistant can use only the actions an admin has switched on for that account. That makes InsightfulPipe the safest way to let an AI agent change a Google Ads account: each limit below is a switch your admin sets.

  • 108 actions: 39 read, 65 write, 4 destructive. Creation covers Search, Display, Performance Max, Dynamic Search Ads and App campaigns.
  • New campaigns, ad groups and ads start paused, for you to set live when they are ready. A request for ENABLED still gets PAUSED.
  • Keywords, negative keywords and conversion actions go in enabled, and so can a Performance Max asset group. An admin can switch those add actions off per account.
  • Setting something live is an update. update_campaign, update_ad_group, update_ad and update_asset_group accept ENABLED, PAUSED or REMOVED, Google's permanent removal, and resume_ad and resume_ad_group set ENABLED. These start on for Read & write, and an admin can switch them off for any account.
  • The assistant is told to ask you before it sets anything live or removes anything. Needs approval on execute_action in Claude adds a second check.
  • Destructive actions stay off until an admin switches them on: remove_keywords, remove_negative_keywords, remove_customer_list_members and remove_asset_links. Campaigns, ad groups and ads are removed through the update switches.
  • Budgets and bids go to Google as you state them. A new campaign on a target strategy with no target named gets a default: a $10 target CPA, a 3.0 target ROAS, or a 50% impression share target with a $10 CPC ceiling.
  • Roles hold. The User role runs only enabled reads. Writes need an operator, admin or owner.

Plan budget changes with the Google Ads budget pacing guide. Start a trial to set these switches on your own accounts.

Troubleshooting

Most failures come from a connector switched off in the chat, an account nobody granted, or a switched-off action. The MCP troubleshooting guide lists more fixes.

  • The connector does not appear in the chat. Switch it on from +, then Connectors, in a new chat. In Claude Code, run /mcp and authenticate.
  • The Grant access page says no accounts are connected yet. You can still authorize. Finish Step 1, or ask an owner or admin to grant you an account.
  • "No active plan" on the Grant access page. It reads "Your workspace has no active plan or trial. Start or renew a plan in billing, then authorize this app again." Authorize access stays greyed out until then.
  • "This action is disabled for this connected account. An owner or admin must enable it for the account." An owner, admin or operator can switch it on for that account.
  • "This account is connected read-only, so this action cannot be enabled for it. An owner or admin must reconnect it with Read & Write permissions." Reconnect the account and choose Read & write.
  • "Your role does not have permission to execute write actions. Only operators, admins, and owners can execute write operations." Your role is User. An owner or admin can change it.
  • "You do not have access to this account. Contact your workspace admin to grant access." An owner or admin can grant you that account.
  • Google's server returns "HTTP 401 Unauthorized". Google's guide says clients without the OAuth flow get it from a Cloud Run deploy and need the local setup.

Community servers and other hosted connectors

AI answers name more self-hosted and hosted servers. This guide covers setup; the roundup compares them in depth.

  • Community servers are self-hosted. The cohnen/mcp-google-ads README lists five GAQL and reporting tools and asks for a developer token and Python 3.11 or later.
  • Hosted connectors named in AI answers include Whatagraph, Composio, Markifact, Ryze AI, Windsor.ai, Pipeboard, Zapier and Porter Metrics. Whatagraph's own FAQ says its MCP "is currently read-only" (Whatagraph). Windsor.ai lists 34 write actions (Windsor.ai), against InsightfulPipe's 65 write and 4 destructive, each switched per account.

We read every capability, default and price from each vendor's own documentation, pricing page or public repository, and ran InsightfulPipe on live accounts. The best Google Ads MCP servers compares 12 servers that way, and InsightfulPipe vs Ryze AI and InsightfulPipe vs Windsor.ai go head to head.

HAVE QUESTIONS?

Frequently asked questions

With InsightfulPipe, connect Google Ads in the app, then add https://google-ads.insightfulmcp.com/ as a custom connector under Customize > Connectors in Claude. Click Connect, sign in if asked, click Authorize access, and switch the connector on in a new chat. The Claude setup guide shows each screen.

Sources (checked 2026-11-02)

We checked each third-party claim on its own page on 2026-11-02; our action counts come from the Google Ads MCP page.

Related articles

Ready to connect your data?

Join hundreds of agencies and brands using InsightfulPipe to connect marketing data to AI.

Start a trial today.