By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Claude Code to Google Ads is the Ryze AI connector. Connect Google Ads in a Ryze AI workspace, run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp in your terminal, then run /mcp inside Claude Code, select ryze and sign in. Start a new session and ask for a Google Ads report.
- In Ryze AI open Integrations, find Google Ads and click Connect with your Google login
- In your terminal run the claude mcp add command with the connector URL
- In Claude Code run /mcp, select ryze and authenticate in the browser
- Pick the workspace, click Allow connection and ask your first question
Claude Code to Google Ads at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, added to Claude Code as a remote HTTP server with one claude mcp add command |
| Server address | https://connector.get-ryze.ai/mcp |
| Sign-in | Browser OAuth started from /mcp or claude mcp login ryze, or a Ryze AI API key sent with --header |
| Google Ads tools | 16: 8 read, 7 write and 1 delete |
| Changes to the account | Yes, when your Google user has Standard or Admin access. An ask rule in Claude Code can hold each change for your approval |
| Google permission asked | One Google Ads scope for read and write, plus openid, email and profile |
| Claude plan needed | Pro, Max, Ultra, Team, Enterprise or Console. Not the free plan |
| Ryze AI price | Paid Ads, $89 per month with a 7-day free trial. Adding the connector is free |
| Google's own option | google-ads-mcp, run on your machine or a Cloud Run service you deploy, with your own Google Cloud project. 7 tools, none that change campaigns, budgets or bids |
| Anthropic Directory | Ryze AI is listed with the Community label since August 2026 |
| Last tested | November 13, 2026: 9 Google Ads calls made from Claude Code |
Before you start
- A Claude Code account. Anthropic says Claude Code requires a Pro, Max, Ultra, Team, Enterprise or Console account; the free claude.ai plan does not include it. It can also run through Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry. Anthropic's MCP page names no extra plan for remote MCP servers.
- A Google login with access to your Google Ads accounts. Standard or admin access is needed to allow changes. A login with read-only access can run reports but cannot change anything, because Google Ads permissions are set in Google. Agencies connect the manager (MCC) login once.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; Agency is $279 per month. Connecting the connector is free, but the Google Ads tools need an active plan or trial.
How to connect Claude Code to Google Ads
Two steps happen in Ryze AI, four in Claude Code. The connector URL is the same for every user.
Connect Google Ads in Ryze AI
Create a Ryze AI account or sign in, open Integrations in the left sidebar and find Google Ads under Advertising. Click Connect, sign in to Google with the login that has access to your ad accounts and approve access with every requested permission checked.
Check the connection
Back in Ryze AI the Google Ads card shows Connected. There is no account to pick: Ryze AI sees every Google Ads account that login can reach. Optionally click View on the card and use Agent default accounts to choose the accounts the agent works with first.
Register the connector in Claude Code
In your terminal run: claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. The server is stored with local scope by default. Add --scope user to make it available in all your projects.
Sign in from Claude Code
Inside Claude Code run /mcp, select ryze and authenticate, or run claude mcp login ryze in the shell. Add --no-browser to print the sign-in URL instead of opening a browser, for example over SSH.
Allow the workspace
On the Ryze AI page, sign in if asked, choose the workspaces Claude Code can use and click Allow connection. Check the result with claude mcp get ryze.
Start a new session and ask your first question
Tool search is on by default in Claude Code, so MCP tools load on demand. Ask: Use GAQL to list my Google Ads campaigns with spend, conversions and conversion value for the last 30 days.
The Ryze AI help article for Google Ads covers the Google side of the connection, and the Claude Code MCP docs cover the client commands. Checked November 14, 2026.
OAuth, API key and claude.ai connectors
Claude Code accepts the Ryze AI connector three ways. Pick the one that matches where the session runs.
CLI with OAuth (recommended for a personal machine)
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope userThis is the flow in the steps above. Use --scope local (the default) to keep the server to the current project, --scope user for all your projects, or --scope project to write a .mcp.json file the team can share. Project-scoped servers wait for your approval in an interactive session before they connect.
CLI with a Ryze AI API key
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --header "Authorization: Bearer rk_live_..."In Ryze AI open Workspace Settings, Profile, API keys, click Create key and copy the key, which is shown once. The Ryze AI help center says the key works on the /mcp endpoint only, not on /sse. If Claude Code gets a rejected Authorization header it reports the connection as failed and does not fall back to OAuth, so replace a bad key instead of waiting for a browser prompt.
claude.ai connectors inside Claude Code
Add Ryze AI at claude.ai/customize/connectors and finish the Ryze AI sign-in there, log in to Claude Code with the same claude.ai subscription account, then run /mcp. Connectors added in claude.ai appear with an indicator that they come from claude.ai. On Team and Enterprise plans only admins can add servers in claude.ai. These connectors load only when the active login is a claude.ai subscription, not with ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, apiKeyHelper or a third-party provider.
Scripts and limits
claude -p and Agent SDK runs cannot run the OAuth flow. Sign in first with /mcp or claude mcp login ryze, or use the API key method. For scripts and your own agents, Ryze AI API keys are the documented route. Claude Code warns when a tool result exceeds 10,000 tokens and limits MCP output to 25,000 tokens by default, saving a larger result to a file; set MAX_MCP_OUTPUT_TOKENS to raise the limit. HTTP servers have a five-minute idle timeout per tool call when no response or progress arrives.
Claude Code and MCP: the facts in one table
| Topic | What Anthropic's documentation says |
|---|---|
| Where entries are saved | ~/.claude.json for local and user scope, .mcp.json in the project root for project scope. To change scope, remove the entry and add it again |
| Transports | HTTP (recommended for remote servers), SSE (deprecated), stdio and WebSocket |
| Sign-in | OAuth 2.0. A 401 or 403 answer marks the server as needing authentication, and the browser hands back to a loopback address on a random port |
| Static keys | --header "Authorization: Bearer ...". The entry is saved without testing the key |
| Tool approval | Auto mode is the starting mode for interactive sessions on v2.1.283 or later, where the session can use it (a supported model, not turned off). A classifier then reviews actions. Rules name tools as mcp__<server>__<tool> |
| Managing servers | claude mcp list, get and remove in the shell; /mcp inside a session for status, sign-in and reconnecting |
| Output limits | A warning at 10,000 tokens. Above the 25,000-token default the result is saved to a file |
| claude.ai connectors | Fetched only under a claude.ai subscription login. An entry added with claude mcp add for the same URL takes precedence |
| Cloud sessions | Local and user scope entries stay on your machine. A cloud session on one repository loads that repository's .mcp.json |
| Finding servers | No registry in the CLI. Any remote server in the Anthropic Directory can be added with claude mcp add |
Sources: Claude Code MCP, Claude Code MCP quickstart, Claude Code permission modes, Claude Code setup, Claude Code cloud environments. Checked November 14, 2026.
Claude web, ChatGPT and Cursor
The same URL works in other MCP clients. Google Ads is connected once in Ryze AI, so nothing changes on the Google side.
Claude on the web and Desktop
Open Customize, Connectors, click + Add, choose Add custom connector, name it Ryze AI and enter https://connector.get-ryze.ai/mcp. Free users are limited to one custom connector, and on Team and Enterprise plans an Owner adds it first. Use Customize, Connectors for this.
ChatGPT
OpenAI says full custom MCP server support is for ChatGPT Business and Enterprise/Edu on the web, and Pro can connect custom MCP servers with read and fetch permissions only. In Plugins choose Add custom MCP server, enter the URL and pick OAuth.
Cursor
Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor runs OAuth with PKCE and asks for approval before using MCP tools by default.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Google Ads permissions and scopes
Three things decide what Claude Code can reach in Google Ads.
- Which Google login
- Ryze AI connects with Google OAuth. Sign in with the Google login that has access to your Google Ads accounts and keep every requested permission checked: the Google Ads scope https://www.googleapis.com/auth/adwords plus openid, email and profile. The login needs access to at least one Google Ads account.
- Which accounts
- One login reaches every Google Ads account it can access, including client accounts under a manager (MCC) login. Accounts the login cannot access, or client accounts under a manager login you did not connect, are out of reach.
- Read or write
- Google Ads permissions are set in Google, not in Ryze AI. A login with read-only access cannot make changes. For a hard read-only guarantee, connect a Google login that only has read access.
The four Google scopes Ryze AI asks for
Ryze AI asks Google for four OAuth scopes. Google Ads has one scope for reading and writing: Google's access model page says the API uses the same scopes for read-only and read-write operations. So the role of your Google user in each account decides what Claude Code can change.
| Scope | Google's description | On this connection |
|---|---|---|
| https://www.googleapis.com/auth/adwords | See, edit, create, and delete your Google Ads accounts and data. | The only Google Ads scope, used for reports and changes alike |
| openid | Associate you with your personal info on Google | Part of the Google sign-in |
| See your primary Google Account email address | Part of the Google sign-in | |
| profile | See your personal info, including any personal info you've made publicly available | Part of the Google sign-in |
Your Google Ads role decides read or write
Google's five user access levels are Email-only, Billing, Read-only, Standard and Admin. A change sent from Claude Code goes through only when your Google user has Standard or Admin.
| What the user can do | Access levels that allow it |
|---|---|
| View campaigns and use planning tools | Read-only, Standard, Admin |
| Edit and run campaign performance reports | Read-only, Standard, Admin |
| Edit campaigns | Standard, Admin |
| Give account access and change access levels | Admin |
| View billing information | Billing, Read-only, Standard, Admin |
For agencies: Google's list of accessible customers shows only the accounts a user reaches directly, so a client account under a manager can be missing from it. Calls to that client need the manager's ID as login-customer-id, which the Ryze AI tools take as loginCustomerId. Without it Google returns AuthorizationError.USER_PERMISSION_DENIED.
Not included: accounts the login cannot open, client accounts under a manager login you did not connect, changes by a Read-only user, video file uploads (a video ad needs a YouTube link), removing people from a Customer Match list, and undoing a removal, since Google Ads has no undo.
Sources: Ryze AI Google Ads guide, Google OAuth 2.0 scopes, Google Ads API access model, Google Ads access levels, Google Ads API call structure, Google Ads API OAuth overview. Checked November 14, 2026.
Removing access
To remove access, click View on the Google Ads card in Ryze AI and disconnect the login, or revoke it on the Google Account permissions page. In Claude Code, run claude mcp logout ryze before claude mcp remove ryze: Anthropic's docs say remove alone deletes the stored tokens without revoking them.
What Claude Code can do in Google Ads
The Ryze AI connector exposes 16 Google Ads tools: 8 read, 7 write and 1 delete. They use Google's official API and run as the Google login you connected.
| Tool | Type | What it does |
|---|---|---|
| google_ads__getAccountSummary | Read | Returns aggregate account metrics for a date range. |
| google_ads__getAccountHierarchy | Read | Returns the manager and sub-account hierarchy for an account. |
| google_ads__listAccessibleCustomers | Read | Lists every Google Ads customer account the connected login can access. |
| google_ads__listConversionActions | Read | Lists the conversion actions in an account. |
| google_ads__listRecommendations | Read | Lists Google Ads optimization recommendations for an account. |
| google_ads__runRawGaql | Read | Runs a raw GAQL query, including change history from change_event. |
| google_ads__generateKeywordIdeas | Read | Generates Keyword Planner ideas from seed keywords, a URL or both. |
| google_ads__generateKeywordHistoricalMetrics | Read | Returns Keyword Planner history (average monthly searches, competition, top-of-page bid range) for a known keyword list. |
| google_ads__runRawMutate | Write | Creates or updates resources such as campaigns, budgets, ad groups, ads, keywords, criteria and assets. |
| google_ads__runRawCustomAudienceMutate | Write | Creates or updates custom audiences based on keywords, URLs, place categories or apps. |
| google_ads__runRawUserListMutate | Write | Creates or updates user lists, including Customer Match lists. |
| google_ads__uploadCustomerMatchMembers | Write | Adds people to a Customer Match list. The server normalizes and SHA-256 hashes every identifier before it reaches Google. It only adds members. |
| google_ads__uploadImageAsset | Write | Uploads an image from a URL as an image asset that can be linked to campaigns, ad groups, asset groups or ads. |
| google_ads__applyRecommendation | Write | Applies Google Ads recommendations. |
| google_ads__dismissRecommendation | Write | Dismisses Google Ads recommendations. |
| google_ads__runRawMutateDelete | Delete | Removes resources. Removals are permanent, and the tool description tells the agent to use it only on an item-by-item approved list. |
Claude Code has its own permission rules. A rule names one tool as mcp__<server>__<tool>, or all of a server's tools as mcp__<server>__*, where <server> is the name you chose in claude mcp add, and it can allow, ask or deny. Recent versions start interactive sessions in auto mode where it is available, and there a classifier reviews actions instead of you, so do not count on a prompt before a change. A call that matches an ask rule still asks: put ask rules on the write tools and the delete tool to approve each change. In the claude.ai connector settings (Customize, Connectors, Ryze AI) you can set write and delete tools to Needs approval, and when an organization sets a claude.ai connector tool to ask and that setting reaches your session, Claude Code prompts on every call. Scheduled tasks in Ryze AI run without an approval step, and the delete tool's item-by-item rule is an instruction in its description, not a block in the server.
Google Ads limits in numbers
Google's numbers apply to any client. The daily counts belong to a Google Cloud project, so they matter most when you run Google's own server on your project. The Ryze AI row comes from the tool definitions listed on November 13, 2026.
| Limit | Value |
|---|---|
| Daily operations per Google Cloud project | Explorer: 2,880 on production accounts. Basic: 15,000. Standard: no cap. A day is a sliding 24 hours |
| What counts as an operation | One Search or SearchStream request, rejected ones included. Follow-up pages fetched with a page token do not count |
| Requests per second | Metered per customer ID and per project; Google publishes no fixed number. Going over returns RESOURCE_TEMPORARILY_EXHAUSTED, and Google suggests backing off 2, 4, then 8 seconds plus jitter |
| Rows per report page | Up to 10,000. A page token expires after about two hours unused |
| Change history | 30 days back, with a date filter and a LIMIT of 10,000 or less. A new change can take up to 3 minutes to show |
| Keyword Planner | 1 request per second per customer ID, and up to 10,000 keywords and 10 locations per history request. Explorer access cannot use it |
| One change request | At most 10,000 mutate operations |
| Data freshness | Clicks, impressions and cost refresh hourly. Conversions under models other than last click arrive later |
| Ryze AI tool inputs | runRawGaql takes a query of 1 to 10,000 characters. uploadCustomerMatchMembers takes 1 to 100,000 members per call |
| Claude Code side | A report above 25,000 tokens is saved to a file, so ask for fewer columns or a LIMIT |
Sources: Google Ads API quotas, API access levels, rate limits, paging, change event, keyword historical metrics, Google Ads data freshness. Checked November 14, 2026. Ryze AI tool inputs as listed on November 13, 2026.
Calls tested from Claude Code
Each row is one call made from Claude Code through the Ryze AI connector on November 13, 2026, on a live Google Ads connection. The account is real, so IDs and numbers are left out. Seven calls carried a deliberate mistake, to collect Google's exact messages.
| Tool | What was sent | What came back |
|---|---|---|
| google_ads__listAccessibleCustomers | No input | Worked. Resource names in the form customers/ plus an ID, not shown here |
| google_ads__generateKeywordHistoricalMetrics | google ads mcp, connect chatgpt to google ads and google ads api, for the United States in English | Worked. Per keyword: average monthly searches, competition, competition index, top-of-page bid range and 12 monthly values |
| google_ads__runRawGaql | The field campaign.daily_budget, which does not exist | Refused: HTTP 400, UNRECOGNIZED_FIELD |
| google_ads__runRawGaql | The resource campaign_experiment, which does not exist | Refused: HTTP 400, UNRECOGNIZED_FIELD |
| google_ads__runRawGaql | A query starting with SELEC | Refused: HTTP 400, EXPECTED_SELECT |
| google_ads__runRawGaql | change_event with no LIMIT | Refused: HTTP 400, LIMIT_NOT_SPECIFIED |
| google_ads__runRawGaql | change_event with LIMIT 10001 | Refused: HTTP 400, INVALID_LIMIT_CLAUSE |
| google_ads__runRawGaql | A made-up 10-digit customer ID | Refused: HTTP 401, CUSTOMER_NOT_FOUND |
| google_ads__generateKeywordHistoricalMetrics | Language and location as bare numbers, 1000 and 2840 | Refused: HTTP 400, RESOURCE_NAME_MALFORMED |
Every refusal was a JSON error with a code, a message, a status and a GoogleAdsFailure detail carrying a request ID, and each HTTP 400 also read "Request contains an invalid argument." The payloads named API version v24. No call returned a quota counter or a rate-limit header.
First 3 prompts to run
Each answer comes from your own account, so this page describes what comes back instead of showing sample numbers.
1. A campaign report with GAQL
Use runRawGaql to list my enabled campaigns with cost, conversions and conversion value for the last 30 days, ordered by cost.
Tools used: google_ads__runRawGaql
What comes back: A table with one row per enabled campaign and the three metrics, sorted by cost. If the output is large Claude Code warns at 10,000 tokens, so narrow the query with a LIMIT or fewer fields.
2. Who changed what
Query change_event for the last 14 days and list which user changed budgets, bids or campaign status, with the time of each change.
Tools used: google_ads__runRawGaql
What comes back: A list of changes with the user, the resource and the time. Change history covers up to the last 30 days, and Google refuses a change_event query that has no LIMIT of 10,000 or less, so the query needs one.
3. Keyword research from a URL
Generate Keyword Planner ideas from my pricing page URL, then pull average monthly searches and competition for the 20 most relevant ones.
Tools used: google_ads__generateKeywordIdeas, google_ads__generateKeywordHistoricalMetrics
What comes back: A keyword list with average monthly searches, competition and the top-of-page bid range from Keyword Planner.
To make a change, ask for it in plain words, for example adding negative keywords or pausing a campaign by name, and set write tools to ask first as described above. Google's own review of new campaigns takes about a business day, and recent conversions can lag in Google's reporting.
10 jobs to hand to Claude Code
Ten jobs to type into Claude Code, with the tool each one calls, named here without the google_ads__ prefix. Two returned data in the test on November 13, 2026: the account list and the keyword volumes. The change log query ran only to collect its two LIMIT refusals, and the other jobs were not run. One Google sign-in covers read and write, and your Google Ads role decides whether a change goes through.
| Job | Ask Claude Code | Tool | Works on the default connection |
|---|---|---|---|
| Spend and ROAS | Show cost, conversions and conversion value per campaign for last month, with ROAS. | getAccountSummary, runRawGaql | Yes |
| Change log | From change_event, list who changed what in the past 14 days, LIMIT 500. | runRawGaql | Yes, up to 30 days back |
| Account map | List every account this login reaches and the manager hierarchy. | listAccessibleCustomers, getAccountHierarchy | Yes. The list call worked in the test |
| Keyword ideas | Suggest keywords from these seeds and this landing page URL. | generateKeywordIdeas | Yes |
| Keyword volumes | Get average monthly searches, competition and top-of-page bids for this list. | generateKeywordHistoricalMetrics | Yes. It worked in the test |
| Conversion setup | List the conversion actions in my main account. | listConversionActions | Yes |
| Recommendations | List Google's recommendations, apply the two I pick and dismiss the rest. | listRecommendations, applyRecommendation, dismissRecommendation | Listing, yes. Applying needs Standard or Admin |
| Campaign edits | Dry-run these negative keywords and a campaign pause with validateOnly, then apply them. | runRawMutate | With Standard or Admin access |
| Customer Match | Create a Customer Match list and add the contacts from the CSV I point you to. | runRawUserListMutate, uploadCustomerMatchMembers | With Standard or Admin access. Adds people only |
| Remove items | Remove these paused ad groups one at a time, after I approve each. | runRawMutateDelete | With Standard or Admin access. Permanent |
5 ways to connect Claude Code to Google Ads
Five ways reach Google Ads from Claude Code. The Ryze AI connector is the main way here: Google is connected once in Ryze AI, and Claude Code needs one command and a browser sign-in, with no Google Cloud project or credentials file. The other four were checked on November 14, 2026.
| Way | Runs where | Setup in Claude Code | What it reaches in Google Ads | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every user, and the same URL serves claude.ai, Claude Desktop, ChatGPT, Cursor and other MCP clients | claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp, then sign in from /mcp. An API key with --header or a claude.ai connector also works | 16 tools: GAQL and change history, Keyword Planner, recommendations, campaign, budget, bid, keyword and ad changes, audiences, Customer Match, image assets and a separate delete tool. Plus the other platforms in the same workspace | Paid Ads, $89 per month with a 7-day free trial |
| google-ads-mcp, Google's open-source server | On your computer over stdio, or a Cloud Run service you deploy, over Streamable HTTP | gcloud auth application-default login with the adwords scope and an OAuth client file (a service account also works), then claude mcp add google-ads-mcp --env GOOGLE_CLOUD_PROJECT=<project> --env GOOGLE_APPLICATION_CREDENTIALS=<file> -- pipx run --spec google-ads-mcp==0.0.6 google-ads-mcp. Needs Python 3.10+, pipx, gcloud and a Google Cloud project with Explorer, Basic or Standard API access. No developer token | 7 tools in 0.0.6: 3 read (accounts, GAQL search built from structured fields, metadata) and 4 for assets, video uploads and labels, each change proposed and then confirmed. Turning off the assets and labels groups in tools_config.yaml makes it read-only. No campaign, ad group, ad, budget or bid changes and no Keyword Planner | No price stated |
| Google Ads API Developer Assistant v4.0.0 | A plugin inside Claude Code. Open source, and its page says it is not an official Google product | Clone google-ads-api-developer-assistant and run ./install.sh claude. Needs Python 3.10+, Git, a Google Cloud project with API access and a google-ads.yaml file with OAuth credentials | Builds and checks GAQL, runs read-only reports to the terminal or CSV, and writes client library code. Changes are saved as code and never run by the assistant | No price stated |
| Composio | Hosted | Its Google Ads page names Claude Code. The hosted address is https://connect.composio.dev/mcp, the kind of remote server claude mcp add --transport http takes, and Google Ads is authorized through Composio's managed OAuth app. The Composio steps read for this guide are for ChatGPT, and this route was not run | 78 Google Ads tools, read and write | Pricing page: the free plan stops at 10,000 tool calls a month, Standard is $18 per seat per month |
| Zapier MCP | Hosted | Zapier lists Claude Code among popular clients. Generate a Zapier MCP URL, pick the Google Ads actions and add the URL as an HTTP server | 2 triggers and 15 actions, among them Create Report, Set Campaign Status and a raw API Request. No dedicated GAQL or campaign-building action | 2 tasks from your Zapier plan per successful call |
Google's guide puts its server in ~/.claude/settings.json, but Anthropic's quickstart names ~/.claude.json and .mcp.json as the files Claude Code reads, so add it with claude mcp add. Google's Cloud Run route lists redirect addresses for Claude, ChatGPT and Antigravity, not the loopback sign-in Claude Code uses. Google's guide describes no endpoint that Google hosts.
Google Ads options that do not fit Claude Code
- Google's agent skills for the Google Ads API. They install in Claude Code with npx skills add google/skills/skills/ads --agent=claude-code, but the page describes no account connection of their own: they teach the agent to use Google's server and client libraries.
- Coupler.io. Read-only, on synced data. Its page names Claude, ChatGPT, Gemini, Perplexity, Cursor, Copilot and OpenClaw, not Claude Code.
- Windsor.ai. Reads and writes back from ChatGPT and Claude. Its page names Claude, ChatGPT, Perplexity, Cursor, Gemini and Copilot, not Claude Code.
- cohnen/mcp-google-ads. Open source, 5 reporting tools. Its README covers Claude Desktop and Cursor, not Claude Code, and still asks for a developer token, which Google's API servers have ignored since the token sunset on September 9, 2026.
Which one to pick
Ryze AI is the best Google Ads connector for Claude Code when you want a hosted URL with sign-in handled for you and campaign changes available, but you pay for a Ryze AI plan and your data passes through Ryze AI. For reports only, with your own Google Cloud credentials, google-ads-mcp needs no Ryze AI plan. The Developer Assistant suits writing Google Ads API code, and Composio and Zapier suit teams that already use them.
Sources: Google Ads API MCP server, google-ads-mcp on GitHub, google-ads-mcp releases, Google Ads API agent skills, Google Ads API Developer Assistant, Developer Assistant on GitHub, Composio Google Ads, Composio pricing, Zapier MCP for Google Ads, Zapier MCP quickstart, Coupler.io Google Ads MCP, Windsor MCP, cohnen/mcp-google-ads, Claude Code MCP, Claude Code permissions, Ryze AI Google Ads guide. Checked November 14, 2026.
Google Ads and Claude Code: dates that matter
| Date | What happened |
|---|---|
| June 18, 2025 | Claude Code 1.0.27 added Streamable HTTP servers and OAuth for remote servers. |
| October 7, 2025 | Google announced its open-source Google Ads API MCP Server, read-only at first. |
| February 18, 2026 | Claude Code 2.1.46 made claude.ai connectors usable in Claude Code. |
| June 22, 2026 | Claude Code 2.1.186 added claude mcp login and claude mcp logout. |
| August 2026 | The Ryze AI listing was added to the Anthropic Directory, which shows the month only. |
| August 24, 2026 | Developer Assistant v4.0.0 became a plugin and added Claude Code support. |
| September 9, 2026 | Google sunset developer tokens. API access now belongs to the Google Cloud project. |
| September 28, 2026 | Claude Code 2.1.284 started interactive sessions in auto mode on every plan and provider when no permission mode is set. Version 2.1.283 had made the change for third-party providers and sessions with telemetry off. |
| November 2, 2026 | google-ads-mcp 0.0.6 added its first tools that change an account, for assets and labels. |
| November 13, 2026 | Google's MCP server guide shows this date as last updated, and Claude Code 2.1.325 came out. |
| May 2027 | Google Ads API v24 sunsets. It is the version named in the error payloads of the test. |
Sources: Claude Code changelog, Anthropic on remote MCP in Claude Code, Anthropic Directory listing, Google Ads Developer Blog, October 7, 2025, Developer Assistant releases, Google Ads developer token, Google Ads API sunset dates, google-ads-mcp releases. Checked November 14, 2026.
How this guide was tested
The connector address was checked on November 13, 2026, at about 04:20 UTC, and nine Google Ads calls were made from Claude Code through the connector the same day.
| What was run | What came back |
|---|---|
| Connector address, no sign-in | HTTP 401 with a WWW-Authenticate header that points to the sign-in details. Claude Code's docs say a server that answers this way is marked as needing authentication. |
| Discovery files | Both loaded: the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and the scopes mcp:read and mcp:write. |
| Live tool list | 16 google_ads tools: 8 read, 7 write and 1 delete. Each takes an optional connection_id, and four have a validateOnly switch for a dry run. |
| Reads with data | Two worked: the account list and keyword history for three keywords. |
| Deliberate mistakes | Seven calls: six GAQL queries, one of them with a made-up customer ID, and one Keyword Planner call with bare IDs. Google answered each one; the messages are in the errors table. |
| Quota and version | No quota counter or rate-limit header came back. The error payloads named API version v24. |
| Search Console | One call collected the phrases people search for about Google Ads connectors, used for the FAQ. No counts are shown. |
Not run for this page: the setup steps inside Claude Code, that is claude mcp add, the /mcp sign-in and the workspace choice. Those steps are written from Anthropic's docs, read on November 14, 2026, and from Ryze AI's own setup steps. No report with account data was run (summary, hierarchy, conversion actions, recommendations, keyword ideas or a GAQL query that returns rows), because the account is real. The write and delete tools were not run, because they change the account, and no quota limit was reached.
Errors and fixes
Exact Google Ads messages from the test
The Google Ads API returned these messages through the connector in the test on November 13, 2026. If one appears in a Claude Code tool result, here is the cause and the next step.
| Message | What it means | What to do in Claude Code |
|---|---|---|
| Unrecognized field in the query: 'campaign.daily_budget'. | No such field on that resource (UNRECOGNIZED_FIELD). The tool description names the right one: campaign_budget.amount_micros, selected FROM campaign. | Ask Claude Code to fix the field name and rerun. |
| Unrecognized field in the query: 'campaign_experiment.name'. | An unknown resource is reported as an unknown field. Experiments live in the experiment resource. | Ask Claude Code to query experiment. |
| Error in query: expected SELECT instead of SELEC. | Malformed GAQL (EXPECTED_SELECT). | Ask again; Claude Code rewrites the query. |
| Change event requests must specify a LIMIT in query and LIMIT should be less than or equal to 10k. | A change_event query without a LIMIT (LIMIT_NOT_SPECIFIED). | Add LIMIT 10000 or lower. |
| Change event requests must specify a LIMIT less than or equal to 10k. | A LIMIT above 10,000. The test sent 10001 (INVALID_LIMIT_CLAUSE). | Lower the LIMIT or split the date range. |
| No customer found for the provided customer id. | The customer ID does not exist (CUSTOMER_NOT_FOUND, HTTP 401). The outer message blames a missing credential, but the same connection answered other calls seconds before. | Run listAccessibleCustomers and use an ID from its list. |
| Resource name '1000' is malformed: expected 'languageConstants/{criterion_id}'. | Keyword Planner needs full names such as languageConstants/1000 and geoTargetConstants/2840 (RESOURCE_NAME_MALFORMED). | Ask Claude Code to resend with full resource names. |
Other problems
- Claude Code says the server failed to connect with an API key
- If a configured Authorization header is rejected, Claude Code reports the connection as failed and does not fall back to OAuth. Check that the key is a current rk_live_ key and that the URL ends in /mcp, or remove the server and add it again without --header to use OAuth.
- claude -p or an Agent SDK run cannot sign in
- Those runs cannot run the OAuth flow. Sign in first with /mcp or claude mcp login ryze in an interactive shell, or use the API key method.
- The server does not load from .mcp.json
- Project-scoped servers wait for approval in an interactive session before they connect. Approve it when Claude Code asks.
- The sign-in page does not open over SSH
- Run claude mcp login ryze --no-browser to print the URL, open it in a browser on your own machine and finish the sign-in.
- No Google Ads tools appear
- Start a new session after connecting. If Google Ads was connected in Ryze AI afterwards, run /mcp to reconnect. Tool search is on by default, so tools are loaded on demand and may not be listed up front.
- The result is very large or lands in a file
- Claude Code warns above 10,000 tokens, and a result over the 25,000-token default is saved to a file, with the file path in the conversation instead. Ask for fewer fields or a LIMIT, or raise MAX_MCP_OUTPUT_TOKENS.
- A call times out
- Claude Code aborts a tool call to an HTTP server after five minutes with no response and no progress. Narrow the date range or the query.
- An account is missing
- Ryze AI sees only the accounts the connected Google login can access. Client accounts under a manager login need that manager login connected. Ask Claude Code to run listAccessibleCustomers to see what the login reaches.
- Changes fail
- The connected Google user may have read-only access. Permissions are set in Google, not in Ryze AI. Reconnect with a login that has standard or admin access.
- Claude says a subscription is required
- The Google Ads tools need an active Ryze AI plan or free trial. Start the trial in Ryze AI and retry.
Terms on this page
- MCP
- The Model Context Protocol. Google's guide calls it an open standard that lets large language models work securely with outside data and applications. Claude Code is the client; the Ryze AI connector is a server.
- GAQL
- Google Ads Query Language: select fields FROM one resource and get rows of attributes, segments and metrics.
- Customer ID and login-customer-id
- The 10-digit number of a Google Ads account, written without hyphens in API calls. login-customer-id is the manager's ID when you work through a manager.
- Manager account (MCC)
- A Google Ads account for managing several other accounts from one place.
- Access level
- For users: Email-only, Billing, Read-only, Standard or Admin. For a Google Cloud project: Test, Explorer, Basic or Standard, which sets its daily API operations.
- Change event
- The API resource behind change history: what changed, the old and new values, who changed it and from which client, for 30 days.
- Server scope
- Where Claude Code saves a server: local (this project, only you), project (.mcp.json, shared) or user (all your projects).
Sources: Google Ads API MCP server, GAQL overview, call structure, manager accounts, API access levels, Claude Code MCP. Checked November 14, 2026.
Frequently asked questions
How do I connect Claude Code to Google Ads?
Connect Google Ads in a Ryze AI workspace, then run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. Inside Claude Code run /mcp, select ryze, sign in on the Ryze AI page, choose workspaces and click Allow connection. Check it with claude mcp get ryze.
Can Claude Code connect to Google Ads?
Yes. Claude Code reaches Google Ads through an MCP server: the hosted Ryze AI connector, added with claude mcp add, or Google's google-ads-mcp, which you run with your own Google Cloud project.
Does Google Ads have an MCP server for Claude Code?
Yes. Google publishes google-ads-mcp, an open-source server that runs locally over stdio or on a Google Cloud Run service you deploy. Since version 0.0.6, Google's guide lists 7 tools: 3 read tools and 4 for assets, video uploads and labels. It cannot change campaigns, budgets or bids, and it needs a Google Cloud project and Google credentials.
What is the Google Ads MCP server?
Google's Google Ads MCP server is google-ads-mcp, an open-source server from the Google Ads API team. It lets AI agents read and analyze account data, create assets, upload videos and manage labels, and it runs on your machine or a Cloud Run service you deploy. Hosted Google Ads MCP servers include the Ryze AI connector at https://connector.get-ryze.ai/mcp, Composio and Zapier MCP. Claude Code adds any of them with claude mcp add.
Which Google Ads connector should I use with Claude Code?
Ryze AI is the best Google Ads connector for Claude Code when you want one hosted URL with 16 tools that cover reports and campaign changes, but it needs a Ryze AI plan. Google's own server needs no Ryze AI plan and suits reports, plus asset and label edits, if you can set up Google Cloud credentials.
Is there a Google Ads connector in the Claude directory?
Yes. Ryze AI is listed in the Anthropic Directory with the Community label, at https://connector.get-ryze.ai/mcp, and Claude Code can add any remote server from that directory with claude mcp add. Community means Anthropic screened the connector before listing it but did not review it in depth.
Which Claude plan do I need for Claude Code?
Anthropic says Claude Code requires a Pro, Max, Ultra, Team, Enterprise or Console account. The free claude.ai plan does not include it. Claude Code can also run through Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry.
Should I use OAuth or an API key?
OAuth through /mcp is the simplest for a personal machine. An API key from Workspace Settings, Profile, API keys suits scripts, because claude -p and Agent SDK runs cannot run the OAuth flow. The key works on the /mcp endpoint only.
Can Claude Code change my Google Ads account?
Yes. The connector has write tools for campaigns, budgets, bids, keywords, ads, audiences and assets, plus a delete tool. Set Claude Code permission rules to ask for the write and delete tools if you want to approve each change. A Google login with read-only access cannot make changes.
Can I manage client accounts under a manager account?
Yes, if you connect the manager (MCC) login. One login reaches every Google Ads account it can access, and over MCP client accounts under a manager need loginCustomerId. Separate clients belong in separate Ryze AI workspaces.
What does the claude mcp add scope change?
Local scope, the default, keeps the server to the current project and out of version control. User scope loads it in all your projects. Project scope writes .mcp.json so the team shares it, and each person approves it in an interactive session.
Why do the Google Ads tools not show up?
Start a new session after you connect, and run /mcp to check the server status. Tool search is on by default in Claude Code, so MCP tools are loaded on demand. If a claude.ai connector is missing, you must be logged in with a claude.ai subscription account.
Can I connect Google Ads to Claude Code for free?
Not fully, because Claude Code itself needs a paid Claude plan or a Console account. Google's google-ads-mcp states no price but needs your own Google Cloud project. The Ryze AI connector is free to add, and its Google Ads tools need an active Ryze AI plan or free trial; Paid Ads is $89 per month with a 7-day free trial.
How much does it cost?
Connecting the connector is free, but the Google Ads tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect Google Ads from Claude Code?
Run claude mcp logout ryze and then claude mcp remove ryze to sign out and remove the server from Claude Code; remove alone deletes the stored tokens without revoking them. To remove Google access, click View on the Google Ads card in Ryze AI and disconnect the login.