BYO-UI
Google Cloud

Looker

Curated anchor platform in business intelligence and semantic modeling with material relevance to the Marcom operating stack and a first-party developer surface.

Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
Representative source ↗Product site ↗
System roleSystem of intelligence
Access maturityAgent-accessible SaaS
Agent postureFirst-party provider
Reference updatedJul 7, 2026
BYO-UI reviewedJul 10, 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

Business-data and LookML interaction; admins explicitly enable tools and permissions govern access

02 · Data you can retrieve

Business-data and LookML interaction; admins explicitly enable tools and permissions govern access

03 · Actions and write paths

Looker's first-party MCP/agent surface includes state-changing tools in the documented capability area: Business-data and LookML interaction; admins explicitly enable tools and permissions govern access. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Authentication model is documented by the vendor; inspect the cited source before implementation. Official Google Cloud docs confirm built-in managed MCP in preview and admin tool allowlisting.

05 · Monitoring, approval, and recovery

Official Google Cloud docs confirm built-in managed MCP in preview and admin tool allowlisting. Official Google Cloud docs confirm built-in managed MCP in preview and admin tool allowlisting.

06 · Gaps and implementation limits

Official Google Cloud docs confirm built-in managed MCP in preview and admin tool allowlisting.

First-party access

Documented surfaces

Looker query and SQL Runner ↗Looker APIs can create and run governed model queries and SQL Runner queries. Effective access depends on Looker models, connection credentials, user permissions, and SQL Runner permission.Source: Looker API Query methodsMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPLooker-managed remote MCPPreview

Role: provider

Read scope: Business-data and LookML interaction; admins explicitly enable tools and permissions govern access

Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Official Google Cloud docs confirm built-in managed MCP in preview and admin tool allowlisting.

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 access1
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Google Cloud ships these experiences.

Single-platform patterns

  • Governed semantic-metrics explorer
  • Executive insight brief
  • Experiment review board
  • Anomaly investigation room
Use in the brief composer →

Multi-platform compositions

  • Looker + warehouse or semantic layer: executive insight brief
  • Looker + 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.

5 recorded sources
MCPRepresentative source
https://docs.cloud.google.com/looker/docs/mcp ↗

Official Google Cloud docs confirm built-in managed MCP in preview and admin tool allowlisting.

Publisher updated
Jul 7, 2026
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

Developer docsSource inventory
https://cloud.google.com/looker/docs ↗

First-party developer documentation or platform overview.

Publisher updated
Jul 7, 2026
BYO-UI reviewed
Jul 10, 2026

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

HomepageSource inventory
https://cloud.google.com/looker ↗

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.

Looker query and SQL RunnerTargeted review
Looker API Query methods ↗

Looker APIs can create and run governed model queries and SQL Runner queries. Effective access depends on Looker models, connection credentials, user permissions, and SQL Runner permission.

Publisher updated
Jun 9, 2026
BYO-UI reviewed
Jul 10, 2026

Targeted first-party access review

Verified fact

Tied to the representative first-party source or targeted access review.

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.