Google

Google Analytics

Google Analytics is an anchor because its managed Data API MCP gives agents governed access to property reporting, realtime reporting, metadata, and request compatibility checks while remaining explicitly read-only.

Analytics, SEO & experimentationSystem of intelligenceBYO-UI-ready platform
An illustration of access surfaces surrounding a governed system.
System roleSystem of intelligence
Access maturityBYO-UI-ready platform
MCP supportOfficial MCP server
Reference updatedJul 7, 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

Authorized Google Analytics properties; standard and realtime report requests; dimensions and metrics metadata; and dimension/metric compatibility checks.

02 · Data you can retrieve

Run standard property reports, run realtime reports, retrieve property metadata, and test whether requested dimensions and metrics can be used together.

03 · Actions and write paths

None in the documented Google Analytics MCP surface. Google states that the server is read-only and cannot edit Analytics configuration or settings.

04 · Authentication and permissions

Use Google-supported remote-MCP authentication such as Application Default Credentials, an OAuth 2.0 client, or a bearer token. The principal needs `roles/mcp.toolUser` (or equivalent `mcp.tools.call`) on the Google Cloud project plus permission to the Analytics properties being queried.

05 · Monitoring, approval, and recovery

Google Cloud IAM can allow or deny individual MCP tools by `tool.name`; Data API property quotas apply to MCP calls. BYO-UI should preserve property ID, date range, dimension/metric definitions, and returned quota state with each result.

06 · Limits and caveats

Only four read tools are documented. Data API Core and Realtime quotas apply by property and project, token use varies with query complexity, Google remote MCP does not support Dynamic Client Registration or OAuth Client ID Metadata Documents, and a current Google notice says remote MCP cannot be used with Cursor because of its callback URI.

Agent access

MCP support

Official MCP serverGoogle-managed remote MCP for the Analytics Data APICurrent managed service

Support: Official MCP server

Read scope: Standard reports, realtime reports, metadata discovery, and dimension/metric compatibility checks for authorized Analytics properties.

Write scope: No documented write scope; the first-party Analytics MCP is read-only.

Authentication: Google Cloud remote-MCP authentication using ADC, OAuth 2.0 client credentials, or an OAuth bearer token; Dynamic Client Registration is not supported.

Approval boundary: No Analytics mutation approval boundary is exposed because the current toolset is read-only. Administrators can still restrict individual MCP tool names with IAM allow or deny policies.

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
Documentation5

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

  • Web-performance and acquisition insight cockpit
  • Executive insight brief
  • Experiment review board
  • Anomaly investigation room
Use in the brief builder →

Multi-platform compositions

  • Google Analytics + warehouse or semantic layer: executive insight brief
  • Google Analytics + CRM or lifecycle platform + work-management system: 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.

9 recorded sources
Developer docsSource inventory
https://developers.google.com/analytics ↗

First-party developer documentation or platform overview.

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

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

HomepageSource inventory
https://analytics.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.

MCPSource inventory
https://developers.google.com/analytics/devguides/MCP ↗

Read-only Analytics MCP behavior and prohibition on editing configuration or settings

Publisher updated
Sep 16, 2025
BYO-UI reviewed
Jul 22, 2026

Read-only boundary reverified from first-party documentation on 2026-07-22

ChangelogSource inventory
https://docs.cloud.google.com/mcp/release-notes ↗

Remote MCP operational changes and known issues

Publisher updated
Jul 17, 2026
BYO-UI reviewed
Jul 22, 2026

Remote MCP operational changes and known issues reviewed from live first-party material on 2026-07-22.

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.