Blog/Guide

Google Ads MCP: setup and first account audit

Connect Google Ads to Claude through Hyper MCP, check account access, and verify your first report before enabling campaign changes.

Guide
Jasper Shine
Jasper Shine
·
8 min read
·
November 16, 2026

A Google Ads MCP server lets an AI assistant query a connected ad account and use the actions that server exposes. For an agency, the useful first task is a report you can reconcile with Google Ads: the right account, the same dates, the same conversions, and no unexplained differences.

Hyper brings Google Ads into a broader marketing platform with customizable agents, skills, research and creative tools. Through Hyper MCP, you can use connected accounts from Claude and other compatible assistants. This guide shows how to connect Google Ads, scope the available actions, and check the first report before asking an agent to change campaigns.

Choose the connection for the job

MCP is the connection protocol. The server determines which accounts and actions your assistant can reach. A server that can retrieve a campaign report does not necessarily have a tool to change that campaign's budget.

Hyper publishes this guide. The comparison below describes documented capabilities checked on November 16, 2026; it isn't a benchmark of model accuracy.

JobHyper MCPGoogle's Google Ads MCP server
Read Google Ads performanceGoogle Ads reporting tools in a connected Hyper workspaceGAQL queries through the search tool
Create or update campaignsDocumented campaign, ad group, ad and keyword actions, subject to enabled tools and account permissionsCurrent tool list covers asset and label writes; campaign and budget editing aren't listed
Connect other marketing accountsOther enabled Hyper integrations share the MCP connectionGoogle Ads scope
Run recurring marketing workHyper agents and tasks can use connected integrationsScheduling depends on the application running the server
Control available actionsPer-tool settings, including DisabledConfigurable read-only mode and tool configuration

Google's server now supports reads and limited writes, including asset creation and label management. It can run locally over stdio or remotely over Streamable HTTP. Older tutorials describing it as entirely read-only or local-only are out of date. See the current Google integration guide and the open-source tool list.

Google also changed API access: developer tokens were sunset on September 9, 2026. A self-hosted setup needs the appropriate access level on the Google Cloud project that owns its credentials. Copying a developer-token tutorial from earlier in the year can send you down the wrong setup path. Google's access guide is the source for current requirements.

Connect Google Ads through Hyper

1. Connect the account you intend to review

In Hyper, connect Google Ads with a Google login that can access the intended advertising account. If you manage multiple clients, write down the client account's customer ID before continuing. A manager account and a client account are different reporting scopes.

For a reporting-only job, a Google login with Read only account access provides a useful platform-level restriction. For campaign management, verify the Google account permissions separately from the tools you've enabled in Hyper. One doesn't replace the other.

Hyper's Google Ads integration documentation describes the available reporting and campaign actions. Treat that as the starting point, then check which tools your connection actually exposes.

2. Configure your MCP server

Open the MCP page in Hyper, select the connected integration, and choose the actions to expose. Begin with reads for account identification, campaign performance and the particular report you need.

Set unused write and destructive actions to Disabled. Hyper's MCP setup documentation distinguishes that enforced block from Requires Approval, whose confirmation behavior over MCP depends on the client. A sentence in a prompt asking the assistant not to change anything is useful guidance, but it doesn't remove a tool's permission.

Copy the endpoint shown on your MCP page into your assistant's supported remote MCP setup and complete authentication. The exact client interface can change. Hyper's MCP overview links the maintained connection instructions and explains the difference between your server endpoint and the Claude directory endpoint.

3. Verify the workspace and account

Start with this prompt. Replace the bracketed values before running it.

Show the active Hyper workspace and Google Ads connection.
Confirm that customer [CUSTOMER_ID] is available.
Return the account name, currency and reporting time zone.
Use read-only tools. Do not create or update anything.
If the account cannot be confirmed, stop and explain what is missing.

Read the returned identity. A successful sign-in alone doesn't establish that the assistant has selected the right client. For agencies with similarly named accounts, retain the customer ID in every subsequent prompt.

Check the first report against Google Ads

Choose a completed reporting period and keep the scope deliberately small. One campaign is easier to reconcile than an account containing Search, Shopping and Performance Max with different goals.

Ask for spend, clicks, conversions and conversion value, plus the selected conversion actions. Then open the same account and campaign in Google Ads with matching dates, time zone and columns. Record any difference before asking for recommendations.

Download the first-report checklist. It is a blank review template, not an account export or an automated test. Fill in both the assistant's value and the value you checked in Google Ads.

CheckWhat to recordPass condition
AccountCustomer ID and nameBoth match the intended client
PeriodStart, end and account time zoneSame period in the assistant and Google Ads
ScopeCampaign ID and filtersBoth reports include the same campaign
CostCurrency and spendAny difference is explained before analysis
Conversion definitionActions and included metricsSame conversion definition on both sides
FreshnessRetrieval time and incomplete datesRecent conversion data is identified as provisional

Don't interpret a conversion mismatch as an MCP failure until you check the reporting definition. Google exposes multiple conversion metrics and conversion-date views. Its conversion reporting reference explains those distinctions.

Three prompts for your first account review

These prompts are examples to adapt, not completed Hyper runs. The account IDs, dates and business context must come from your own account.

Campaign performance with a clear comparison

For Google Ads customer [CUSTOMER_ID], compare [START] to [END]
with the preceding period of equal length.
Return campaign ID, name, status, spend, clicks, conversions,
conversion value, cost per conversion and conversion value / cost.
State the currency, time zone, conversion actions and any filters.
Calculate ratios from totals. Mark unavailable values as unavailable.
List observations separately from possible explanations.
Use read-only tools and make no account changes.

Save the query, filters and retrieval time with the report so another buyer can repeat the comparison. The observation might be that cost per conversion increased. A proposed cause, such as weaker lead quality or a changed landing page, needs separate evidence.

Search terms worth reviewing

For customer [CUSTOMER_ID], retrieve the available search terms
for [START] to [END], with campaign and ad group IDs, spend,
clicks and conversions. Explain any coverage limits.
Use this business scope: [WHAT WE SELL, WHERE, AND WHO WE SERVE].
Group terms into relevant, clearly irrelevant and needs review.
For each candidate exclusion, show the reason and proposed scope.
Do not add negative keywords.

A zero-conversion term is a candidate for investigation. It can still describe a valuable buyer, especially when conversion reporting is delayed or the sample is small.

A client-ready decision draft

Using the verified report, draft a weekly update with:
1. The account, dates and conversion definition.
2. The largest material changes, with old and new values.
3. Evidence for each explanation and anything still unknown.
4. Proposed actions, their campaign IDs and the reason for each.
5. A separate list of actions actually completed, if any.
Do not send the update or change the account.

For the wider reporting process, pair this with the agency reporting tools guide.

Troubleshooting the connection

SymptomCheck first
Connected, but the client account is missingThe selected Google login, manager relationship and customer ID
Reporting works, but an edit isn't availableThe server's actual tool list, Hyper tool settings and Google account permissions
An assistant proposes a budget change with Google's serverWhether a supported budget-write tool exists; reasoning about a change isn't execution
The reported cost looks wrongCurrency, date range, filters and any unit conversion in the returned API data
Conversions differ from the Google Ads interfaceConversion action selection, metric definition, conversion-date versus interaction-date reporting and freshness
A self-hosted server can't access production accountsThe Cloud project's Google Ads API access level

The Meta Ads MCP guide covers the adjacent platform. Keep the platform-specific setup and reporting rules separate even when one assistant accesses both.

How Hyper helps

For a recurring account review, give a Hyper agent the customer ID, reporting period, conversion definition and the reconciliation checklist above. Configure the task to retrieve the report and draft the decision log on your review schedule. Keep its available tools limited to the actions that task needs.

Start with one account and a report you can verify. Once that works, add the recurring task and only the write actions the job needs. Hyper pricing: Free 7-day trial, then 49 USD/month.

Autonomous marketing

Grow your business faster with AI agents

  • Automates Google, Meta + 5 more platforms
  • Handles your SEO end to end
  • Improves website conversions
  • Runs social media for you

Frequently asked questions

Q: Is there an official Google Ads MCP server?

Yes. Google publishes googleads/google-ads-mcp. Its current documented scope includes reporting plus limited asset and label writes. It supports local stdio and remote Streamable HTTP deployment.

Q: Can I manage Google Ads from Claude with Hyper?

Hyper MCP exposes the Google Ads tools enabled in your workspace to a compatible Claude connection. Documented actions include reporting and campaign management. Available actions still depend on your connection, tool settings and Google account permissions.

Q: Does Requires Approval block every unapproved MCP write?

Do not assume that. Hyper's documentation says confirmation over MCP depends on the AI client. Disabled is the setting to use when an action must not be callable. Verify the client's behavior before enabling writes.

Q: What should I test after connecting?

Confirm the workspace and customer ID, then compare a single campaign report with Google Ads using the same dates, time zone, currency and conversion definition. Resolve differences before relying on recommendations or enabling account changes.

Tags:Guide

AI Agents for Marketing Magic