How to Connect Google Ads to Claude with MCP
Connect Google Ads to Claude with the Data Bloo MCP and pull impressions, clicks, cost and conversions straight from the chat. No developer token, no Google Cloud project, no terminal, paste one URL and sign in. Here's the 2-minute setup.
The Data Bloo connector
Open the Data Bloo listing in Claude's directory, hit Connect and sign in. There's no server URL, no client ID and no API key anywhere in this setup. Everything below is just where to click.
What connecting Google Ads to Claude actually means
You can ask Claude about your Google Ads and get a real answer, pulled from your actual account, in seconds. Type "how did my Google Ads do last month" and Claude reads your numbers and tells you, no CSV export, no dashboard to open. The connection runs through the Data Bloo MCP, takes about two minutes to set up, and it's read-only, so Claude can analyze your campaigns but can never change them.
Google publishes its own Google Ads MCP server, and it's good, but it's built for developers. It wants a 22-character developer token, a Google Cloud project, OAuth credentials and Python on your machine, and you query it in GAQL. Data Bloo is the no-code route: paste a URL, sign in once, ask in plain English. Same data, none of the setup, plus every other channel alongside it.
Stop exporting Google Ads. Start asking.
The same Google Ads account you already trust for your Data Studio reports, now answering questions in a chat. No exports, no dashboards to open.
Ask, get instant answers
"Which Google Ads campaigns had the highest CTR last week?" Claude pulls the numbers and explains them.
Reports inside the chat
Ask for a 30-day Google Ads view and get tables plus a summary ready to share, no Data Studio setup.
Client-ready summaries
"Turn the last 30 days of Google Ads into an executive summary." Paste it into Slack, email or a doc.
Diagnose dips fast
"Why did our cost jump on Tuesday?" Claude looks across campaigns, ad groups and dates and explains it.
Blend beyond Google
Line Google Ads up against Facebook Ads, TikTok Ads, Search Console or WooCommerce in one answer.
Connect once, use everywhere
The same Google Ads account you linked for Data Studio is instantly available to Claude, zero duplicate setup.
Google Ads, plus every other connector
Already connected in Data Bloo? It's instantly available to Claude, connect once, use everywhere.
Three ways to connect Google Ads to Claude
There are three real options, built for different people. Here's the honest version, including the case where the answer isn't us, so you pick the right one the first time.
A connector like Data Bloo
Paste one URL, sign in once, ask in plain English. No developer token, no Google Cloud project, nothing to host. Read-only, blends across channels, and the same connection feeds your Data Studio reports.
Google's official MCP
Google open-sourced its own Google Ads MCP server on October 7,2025 at github.com/googleads/google-ads-mcp. Free, Apache-2.0, and read-only like ours. The trade-off: it's a developer tool, a 22-character developer token, a Google Cloud project, OAuth credentials, Python, and GAQL to query it.
A manual CSV export
Pull a report from Google Ads, save the file, upload it to Claude. Free, and it works once. Then you do it again next week, separately for every account.
Data Bloo vs Google's official MCP vs a manual export
The bottom line: if you're a developer who wants raw Google Ads API access and GAQL doesn't scare you, Google's own server is free and very good. If you'd rather skip the developer token entirely, ask in plain English, and see Google Ads next to the rest of your marketing, that's Data Bloo.
When to use Google's official MCP instead
Data Bloo isn't the right tool for everyone, and Google's own server is genuinely good. The Google Ads API team open-sourced it on October 7,2025 under Apache-2.0 at github.com/googleads/google-ads-mcp. It exposes three tools, list_accessible_customers, search and get_resource_metadata, and gives you the whole Google Ads API surface. If you want every field the API has ever returned, and you're happy writing GAQL, use it. It's free, and you can't beat first-party coverage.
The trade-offs are real, and they're all about setup. Before you can ask it anything you need a 22-character developer token with at least Explorer access, a Google Cloud project with the Google Ads API switched on, OAuth credentials, and Python installed, then you host the server yourself, locally or on Cloud Run. It also only sees Google Ads, so it can't line your campaigns up against Facebook, Search Console or your store revenue, and it won't feed the Data Studio dashboards you already send clients.
So it's not a safety question, both servers are read-only and neither can touch your budgets. It's a question of who you are. If you're an engineer building on the Google Ads API, take Google's. If you're a marketer who wants an answer before the standup, take the one that's already hosted.
What you need
Three things, and you probably already have them.
How to connect Google Ads to Claude
Pick your Claude client. Desktop & Web are easiest for most marketers; Claude Code is a one-liner for developers.
Go straight to Data Bloo in the Claude directory. You’ll see what it does and every source it supports.
Open Data Bloo in Claude →The Connect button sits at the top right of the listing. It works the same on claude.ai and Claude Desktop.
Claude opens Data Bloo’s sign-in page. Log in with your Data Bloo account and approve read access. Nothing in your accounts can be changed.
Try: "Using Data Bloo, show me my key metrics for the last 30 days and what changed." Claude returns a table plus a short analysis you can share.
Open your terminal and run:
claude mcp add --transport http databloo https://mcp.databloo.com/mcp
Next time you start a Claude Code session, Claude opens your browser to sign in to Data Bloo. Sign in once, the connection persists across sessions.
Run /mcp list, you should see databloo with status connected.
Confirm it works: in a fresh chat, ask "Using Data Bloo, list all the data source accounts I have connected." If Claude returns your accounts, you're fully connected.
Take the MCP for a spin
Walk through connecting Google Ads to Claude and pulling a report, no signup, right here in the page.
Seven read-only tools, and no GAQL to learn
You just ask in plain language, Claude picks the right tool. The typical flow: list_data_sources → get_connector_accounts → list_fields → query_data.
get_userlist_data_sourcesget_connector_accountslist_fieldsquery_datalist_accountsget_datesRead-only, always. Claude can pull and analyze your Google Ads, it can never pause a campaign, edit a bid or change any account setting. There is no write path to switch off, because there isn't one.
No setup tax and all your dashboards in one connection
Every other route to Google Ads in Claude asks you to become a developer first, or to keep exporting by hand. Data Bloo asks for neither. It reads, it reports, and the exact same connection already powering your Data Studio dashboards now answers questions in Claude.
Nothing to install, nothing to host
No developer token to request, no Google Cloud project to stand up, no OAuth JSON to paste into a config file, no Python. You add one URL to Claude and sign in. All seven tools are read-only, so Claude can pull and analyze your Google Ads but can't pause a campaign, move a bid or change a setting.
One connection, two surfaces
The Google Ads source you built for Data Studio is the same one Claude reads. No second setup, no second bill, and the numbers Claude quotes always match the dashboards you send clients. It's the one thing a Google-Ads-only developer tool structurally can't give you.
What Claude actually gives you back
Three real prompts and the kind of answer Claude returns once Google Ads is connected through Data Bloo, numbers, then a plain-language read.
Claude: Last 30 days on Google Ads, 842,110 impressions, 34,180 clicks and €21,940 spent. That's a 4.06% CTR at €0.64 CPC, up 7% on the prior period.
Claude: Highest, Brand · Exact at 11.2% CTR. Lowest, Generic · Broad Match at 1.4%. Brand pulls roughly 8× the click-through at about a fifth of the CPC.
Claude: Search, €13,160 cost, 812 conversions, €16.21 cost per conversion. Shopping, €8,780 cost, 415 conversions, €21.16 cost per conversion.
Example outputs shown for illustration; your figures come live from your own connected account.
What do you want to create?
Pick a format, a source and an account. Data Bloo uses AI to build it with your numbers and your branding.
Data Studio
Opens a template in Data Studio, already connected to this account.
Previewing
What Google Ads data you can pull
The same metrics you use in your reports, sliced by campaign, ad group, keyword, network, device, country and date.
Impressions, clicks, CTR, average CPC, CPM and cost, the top line of every Google Ads report.
Conversions, conversion rate, cost per conversion and conversion value, so ROAS comes through wherever your account tracks value.
Campaign, ad group, keyword, search term, network, device, country and date.
Google Ads spans Search, Shopping, Display, YouTube and Performance Max, split them with the network breakdown to see each campaign type on its own terms.
Ask Claude to list the fields for your account first, it confirms exactly what's available before it queries.
Prompts to paste into Claude
Once connected, drop any of these into a fresh chat. Name Data Bloo in your first message, then drill in.
Built for how you actually work
Same connection, different job to be done. Here's the prompt each type of marketer tends to start with.
Agencies
Pull and compare across every client account without switching logins, then draft the monthly report in the chat.
E-commerce & DTC
Track ROAS and purchase value by campaign, spot the sets quietly burning budget, and line spend up against store revenue.
Lead gen & B2B
Watch leads and cost per lead by campaign, and catch a rising cost per lead before it eats the month's budget.
Common issues and fixes
You're likely not signed in yet, or Google Ads isn't connected in Data Bloo. Ask "Using Data Bloo, list the accounts I have connected." If it comes back empty, open Data Bloo, confirm your Google Ads source is connected, then try again.
Small gaps are normal. Conversions are credited back to the day of the click, so recent figures keep moving for days after the fact, and your account time zone decides which day a number lands in. For trends, comparisons and reporting the Data Bloo pull is solid; for the last few hours of a live campaign, the Google Ads UI is freshest.
ROAS only exists where your conversion actions carry a value. If they don't, Data Bloo omits it rather than showing a misleading zero. Ask for cost and conversions instead, or set conversion values in Google Ads.
That's on purpose, the connection is read-only. Google's official MCP is read-only too, so no MCP route will change your account today. To act on a campaign, use the Google Ads UI or the API directly.
Query notes & FAQs
It's free to start, no credit card. The free tier includes MCP access with usage limits; paid plans raise the limits and add more connected accounts.
No. All seven MCP tools are strictly read-only. Claude can pull and analyze your data but can never edit campaigns, bids, budgets or any account settings. Google's own Google Ads MCP is read-only as well, so no MCP route can change your account right now.
Yes. Google open-sourced one on October 7,2025 at github.com/googleads/google-ads-mcp, under Apache-2.0. It's read-only and it's free, but it's built for developers: you need a 22-character developer token, a Google Cloud project with the Google Ads API enabled, OAuth credentials and Python, and you query it in GAQL. Data Bloo is the hosted, no-code alternative, one URL, plain English, plus your other channels.
Any MCP-compatible client, Claude Desktop, Web and Code, plus ChatGPT, and Gemini. The same URL works across all of them.
Yes. As long as they're connected in Data Bloo, ask Claude to compare Google Ads against TikTok Ads, LinkedIn Ads, Search Console or your WooCommerce revenue, and it pulls one blended answer.
Claude queries your data live through Data Bloo's connectors the moment you ask, subject to each platform's API freshness and your plan's refresh limits.
No. A free Claude account is enough to add the Data Bloo connector and start pulling Google Ads reports. Your Claude plan is separate from Data Bloo, and the connector works on Claude Desktop, Web and Code.
Yes. You sign in once through Data Bloo's secure OAuth flow, and the connection is strictly read-only. Claude can pull and analyze your Google Ads but can never pause a campaign, change a bid or touch a budget, there's no write path in the connection at all.
Yes. Ask Claude to list your connected Google Ads accounts, and it can pull and compare across them, handy for agencies running multiple clients.
Yes. Pair the MCP with Claude's scheduled tasks or Claude Code for an automatic Monday-morning KPI digest, anomaly alerts or a recurring client update, unattended.
Pick how many accounts. Everything else is included.
Every data source, every destination, the Data Bloo MCP and white-label reports come with every paid plan.
Chat with your Google Ads today
Connect Google Ads to Claude in under 2 minutes and pull reports straight from the chat. Free to start, no credit card.