Connect Google Ads to Claude
Connect Google Ads to Claude
Connect Google Ads to Claude through Adrails to read, launch and change campaigns. Ask about spend, structure and keywords. Connect your ad account in Adrails, add https://adrails.ai/api/mcp to your assistant, then sign in and choose your workspace. See the action controls below.
Put it into practice
Free files. No sign-up required.
A Claude setup checklist, two prompts, a result check and troubleshooting. Use your own account and completed dates.
Download the connection checklistTwo synthetic weeks from Example store, with dates, currency, purchases and the calculations used below. No customer data.
Download the example result
01
How to connect Google Ads to Claude
To connect Google Ads to Claude, connect the Google Ads account in Adrails, then add the MCP server in Claude.
On claude.ai and in the Claude desktop app, the connection is a custom connector. Under OAuth client, keep Use Claude's published identity, the recommended option: Adrails reads Claude's client details from the document Anthropic hosts, and there is no client ID, secret or API key to copy. On a Claude Team or Enterprise plan, an owner of your Claude organization adds the connector first, under Organization settings, then Connectors.
Every client uses the same server URL, https://adrails.ai/api/mcp, and the same sign-in: Claude registers itself, you sign in to Adrails, then choose the workspace and the permissions on the consent screen. Google Ads needs nothing on the Claude side, since it is already connected in that workspace under Ad accounts.
- 1. Open Customize, then Connectors, choose Add, then Add custom connector
- 2. Name it Adrails, paste https://adrails.ai/api/mcp as the server URL and keep Use Claude's published identity under OAuth client
- 3. Add the connector, then connect it: Adrails opens, you sign in, choose the workspace and the permissions, and choose Allow access
- 4. In a conversation, open the plus menu, then Connectors, enable Adrails and ask your first question
02
Start with one account and a read-only question
First connect the Google Ads account in Adrails and wait for its initial synchronization. You need access to that account and the intended Adrails workspace. Claude connects to Adrails; adding the MCP server alone does not connect an advertising account.
After signing in, select read access for this first check. Ask: List the Google Ads accounts available in this workspace. Show their IDs, currencies and time zones. Make no changes.
Choose the returned account ID. Then ask: For this account, compare October 5 to 11, 2026 with September 28 to October 4, 2026. Show spend, purchases, purchase revenue, CPA and ROAS. State the currency, time zone, purchase definition and data freshness. Identify missing data. Make no changes. Replace these example dates with two completed weeks for your review.
03
Check the first answer before interpreting performance
The worked result below uses invented Google Ads data from Example store (synthetic), in USD and America/New_York. It demonstrates a review, not a live Claude connection or an account benchmark.
Spend rose 20% while purchases fell 20%. CPA rose from $20 to $30, a 50% increase. Check conversion lag and campaign-level changes before deciding what caused it.
Check the answer against the source report for the same account, dates and purchase definition. If the selected result is a lead rather than a purchase, ask for that distinction and do not label its cost as purchase CPA. Missing purchase revenue must remain unavailable, not zero. Recent conversions can arrive later.
04
Resolve the first connection problem
Use the symptom to choose the next check. Repeating the same performance question will not repair a missing account or permission.
- No custom connector option: check your Claude plan and organization policy with the workspace owner.
- Authentication required: reconnect from the assistant and choose the intended workspace. Do not paste an access token into the conversation.
- No accounts returned: check the advertising connection and initial sync in Adrails. A connected MCP client is a separate connection.
- Tool not available: enable Adrails in this conversation and refresh the client's tool list. The first review needs read access, not advertising write access.
- Numbers disagree: align dates, account currency, time zone, conversion definition and data freshness before drawing a conclusion.
05
What Claude reads from Google Ads
Google Ads is connected once in Adrails, under Ad accounts, by signing in with a Google account that can access your Google Ads accounts. Adrails reads campaigns with their type, status, budget and bidding, ad groups with their keywords, ads with their copy and final URLs, the account's picture library and audiences, and Keyword Planner volumes and ideas, and Claude reaches the same data through the MCP server, with your sign-in and inside the one workspace you chose.
In Claude, the Google Ads reads come from 7 tools: reporting_overview, performance_period, campaigns_structure, google_ads_library, google_keyword_planner, targeting_options and findings_review. The table above says what each one returns and gives a question to type as it is. Every result comes back twice, as exact data for the model and as a readable table for you, so a figure Claude states can be traced to the call that produced it.
06
Three questions to start with
Ask in your own words: Claude picks the tool, Adrails returns the figures, and Claude's model does the reasoning. MCP tool calls cost 0 credits. Each result carries the exact data in structuredContent.result and the same figures as readable tables.
A question can be narrowed to some of the workspace's ad accounts with accountIds, never widened to accounts outside it. A result is at most 256,000 bytes, so a long period at the ad level is asked for in shorter ranges or one campaign at a time.
- What did the Search campaigns spend last month, and at what CPA?
- What are the monthly searches and top-of-page bids for these keywords in Germany?
- Prepare a Search campaign for our new product page with three ad groups, paused.
07
What happens when you ask for a change
No tool creates, edits, pauses, switches on or rebudgets a campaign, ad set or ad by itself. In Claude, google_ads_build creates a Search, Display, Demand Gen, Performance Max or Shopping campaign with its ad groups, keywords and ads or its asset groups, or new ad groups and ads under what exists, all paused after Google validates the request; google_ads_edit changes ad texts, final URLs, keywords, names, campaign dates, target CPA or ROAS, extensions, places, languages, search themes and audience signals, validated by Google when prepared and again when applied, all or nothing; campaigns_change_budget raises or lowers a campaign budget by at most 30% in one change unless you give the amount, and refuses a budget shared between campaigns.
Then campaigns_set_status pauses or resumes one campaign, ad group or ad and measures the result after 24 hours, 3 days and 7 days; campaigns_duplicate_to_draft duplicates a campaign paused, with its targeting, bidding, budget, extensions, keywords and ads. Each of them returns a proposal: a preview of the exact change and a link to the Review advertising change page in Adrails, where you, signed in as an owner or admin of the workspace, apply it or decline it. Adrails reads Google Ads again first and applies the change once, or blocks it if the entity moved in the meantime.
A launch is built paused, switching it on is a second proposal that lists every budget that starts spending, an applied change can be undone while the platform still matches what Adrails wrote, and a proposal expires 24 hours after it is prepared. When Claude asks you to allow the tool call, that is Claude's own setting: allowing it applies nothing, and the change keeps waiting on its page in Adrails.
08
Permissions, cadence and limits
Read workspace data is required and covers every ad account of the workspace; Prepare advertising changes is a separate permission that only an owner or admin can grant, and a permission never goes beyond your role. A member who connects Claude reads Google Ads but sees no write tool.
Structure, findings and overviews come from the account's last synchronization, and performance_period reads an exact date range from Google Ads. accounts_list shows each account's last snapshot, and an owner or admin who granted Manage integrations can queue a refresh with accounts_sync. A Google Ads connection made before Adrails could send conversions cannot send them; connecting Google Ads again from Ad accounts allows it.
Calls on one connection run one at a time, at most 60 a minute per access token, and a connection works in the one workspace you chose at consent: to work in another, connect Claude again and choose it. Revoke Claude under Your connections on the MCP page in Adrails; removing the server in Claude does not revoke it there.
Worked first read
Google Ads: two weeks, one account
| Period (2026) | Spend (USD) | Purchases | Purchase revenue (USD) | CPA (USD) | ROAS |
|---|---|---|---|---|---|
| Sep 28 to Oct 4 | $2,000 | 100 | $8,000 | $20 | 4.00x |
| Oct 5 to 11 | $2,400 | 80 | $6,400 | $30 | 2.67x |
Synthetic example. Both periods use the same purchase definition and account time zone. Platform-attributed revenue is not profit; no advertising changes are performed.
Google Ads tools
What Claude can ask Adrails about Google Ads
| Tool | What it returns | Example question |
|---|---|---|
| reporting_overview | Spend, attributed revenue and named conversion events for the connected accounts, Meta and Google Ads alike, each in its latest synchronized window | What did the Search campaigns spend last month, and at what CPA? |
| performance_period | One account's spend, results, revenue, ROAS, CPA, impressions, clicks, CTR, CPC and CPM over an exact date range, at the account, campaign, ad group or asset group, or ad level | Compare this quarter with the last one at the campaign level. |
| campaigns_structure | How the account is built from the last sync: campaigns with type, status, budget and bidding, ad groups with their keywords, ads with copy, final URL and review | List the ad groups and keywords of the Brand campaign. |
| google_ads_library | The account's picture library, with asset ID, address and size, and its audiences, to reuse in a build or name as an audience signal | Which pictures and audiences does this account already have? |
| google_keyword_planner | Monthly searches and the top-of-page bid range of your keywords, or keyword ideas from a few words or a page, for the countries and language you name | What are the monthly searches and bids for these ten keywords in Germany? |
| targeting_options | The real Google Ads IDs of custom audiences, interests, languages or locations that match a query, as candidates | Find the location IDs for Lyon, Lille and Nantes. |
| findings_review | What the rule engine found on the selected campaigns, each finding with its evidence, snapshot date, objective, currency and severity | What tracking or targeting findings are open on my Google Ads campaigns? |
From the Adrails MCP tools reference and the Google Ads integration documentation on 4 October 2026.
Read more
- MCP connection instructionsClient setup, authentication and workspace permissions.
- Review the account findingsKeep evidence and next actions in a downloadable manual audit.
- Google Ads MCP serverRead the tool contract before preparing any advertising changes.
- Meta Ads MCP serverRead Meta results and prepare campaign changes for review in Adrails.
- Claude integrationClaude with Adrails: setup, the 78 tools and the controls, for every source of the workspace.
- Google Ads in AdrailsWhat Adrails reads, builds and edits on Google Ads, and what Google validates before anything is created.
- MCP tools referenceEvery tool, its inputs and who can call it.
Common questions
Does Claude need an API key for Google Ads?
No. Google Ads is connected once in Adrails, under Ad accounts, by signing in with a Google account that can access your Google Ads accounts. Claude signs in to Adrails with OAuth, with no client ID or secret to copy, and tool results never contain provider credentials or Adrails tokens.
Can Claude change my Google Ads data?
Not by itself. Claude prepares the exact change, and an owner or admin signed in to Adrails applies it from the Review advertising change page; the prompt Claude shows in the conversation before a tool call is its own setting and applies nothing.
How fresh is the Google Ads data?
Structure, findings and overviews come from the account's last synchronization, and performance_period reads an exact date range from Google Ads. accounts_list shows each account's last snapshot, and an owner or admin who granted Manage integrations can queue a refresh with accounts_sync.
Can I connect several Google Ads accounts?
A Claude connection covers every Google Ads account of the workspace, and accountIds narrows a call to some of them.