Google

Google Ads

Google Ads is an anchor for paid-search and performance-media analysis because Google publishes a first-party, self-hostable MCP server for account discovery and GAQL reporting, alongside a separately authorized API that can manage campaigns, ad groups, ads, keywords, and budgets.

Advertising & media buyingSystem of engagementBYO-UI-ready platform
Representative source ↗Product site ↗Suggest a correction
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityBYO-UI-ready platform
MCP supportOfficial MCP server
Reference updatedJun 29, 2026
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

The MCP server exposes accessible Google Ads customers, GAQL search results for resource fields, metrics, budgets and status, and metadata describing Google Ads API resource types.

02 · Data you can retrieve

List customer IDs and account names available to the authenticated principal, execute GAQL queries for resource data and performance metrics, and inspect queryable resource metadata. The current MCP release is strictly read-only.

03 · Actions and write paths

No Google Ads MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.

04 · Authentication and permissions

The MCP server supports OAuth 2.0 or a service account and requires a Google Cloud project plus a Google Ads developer token. The authenticated user or service account must already have access to each Google Ads customer account queried.

05 · Monitoring, approval, and recovery

Keep MCP responses visibly read-only. Any move from analysis to mutation must cross into a separately configured Google Ads API client whose developer-token access level, permissible use, OAuth principal, customer hierarchy, and quotas authorize that action.

06 · Limits and caveats

Current MCP mode is read-only, Python-based, and served over stdio when run locally. Google documents customer-run deployment on Cloud Run or other infrastructure, not a Google-operated remote Ads MCP endpoint. Underlying API calls still use developer-token access levels and system or service quotas.

First-party access

Documented surfaces

Google Ads Query Language ↗The Google Ads MCP search tool executes GAQL requests for resource metrics, budgets, and status. The documented MCP server is read-only; accessible customer accounts, OAuth scopes, GAQL grammar, field compatibility, quotas, and reporting limits apply.Source: Google Ads MCP server: Developer integration guideAPI ↗Developer accessProduct ↗Native platform experience

Agent access

MCP support

Official MCP serverOfficial self-hosted MCPCurrent release

Support: Official MCP server

Read scope: `list_accessible_customers`, GAQL `search` across authorized resources and metrics, and `get_resource_metadata`; all are read-only in the current release.

Write scope: No MCP writes verified; the documented surface is read-only.

Authentication: OAuth 2.0 user credentials or a service account, plus a Google Ads developer token and Google Cloud project. Google Ads API calls use the `adwords` OAuth scope; manager-account calls also identify the login customer.

Approval boundary: No approval dialog can turn the current MCP server into a writer. A proposed bid, budget, campaign, ad, or keyword change must be handed to a separately authorized API or native-UI workflow and confirmed in the correct customer account.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Google ships them.

Single-platform patterns

  • Paid-search diagnostic and budget review cockpit
  • Campaign exception cockpit
  • Creative and policy review queue
  • Budget pacing workbench
Use in the brief builder →

Multi-platform compositions

  • Google Ads + CRM or revenue system: campaign exception cockpit
  • Google Ads + analytics or warehouse + creative-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
APISource inventory
https://developers.google.com/google-ads/api ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Dec 10, 2025
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://ads.google.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.