Google Cloud

BigQuery

Curated anchor platform in cloud data warehouse with material relevance to the Marcom operating stack and a first-party developer surface.

Automation, data & MCP bridgesSystem of orchestrationAgent-accessible SaaS
System roleSystem of orchestration
Access maturityAgent-accessible SaaS
Agent postureFirst-party provider
Reference updatedNot stated by publisher
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

Run SQL queries, retrieve metadata and list BigQuery resources; additional service-specific MCP endpoints exist

02 · Data you can retrieve

Run SQL queries, retrieve metadata and list BigQuery resources; additional service-specific MCP endpoints exist

03 · Actions and write paths

BigQuery's first-party MCP/agent surface includes state-changing tools in the documented capability area: Run SQL queries, retrieve metadata and list BigQuery resources; additional service-specific MCP endpoints exist. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data. Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary.

05 · Monitoring, approval, and recovery

Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data. Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data.

06 · Gaps and implementation limits

Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data.

First-party MCP tool catalog

6 named MCP tools · BigQuery core managed MCP server

The exact tools published for the managed bigquery.googleapis.com/mcp endpoint; Data Transfer Service and Migration are separate server variants below. Reviewed Jul 10, 2026. Invocation requires Google OAuth and IAM permissions. Query jobs bill the project supplied in the request. execute_sql_readonly accepts SELECT only; execute_sql can run DML, DDL, and AI or ML statements and therefore requires explicit confirmation.

First-party exact listComplete list on cited pagebigquery.googleapis.com/mcp
Dataset and table metadata4
list_dataset_idsreadget_dataset_inforeadlist_table_idsreadget_table_inforead
SQL execution2
execute_sql_readonlyreadexecute_sqlconsequential write

First-party MCP tool catalog

13 named MCP tools · BigQuery Data Transfer Service managed MCP server

The exact tools published for the separate bigquerydatatransfer.googleapis.com/mcp endpoint. Reviewed Jul 10, 2026. This is a service-specific MCP endpoint, not an extension of the core endpoint's live catalog. Creating, updating, or deleting transfer configurations and starting or deleting runs can change scheduled data movement, incur costs, and affect downstream datasets.

First-party exact listComplete list on cited pagebigquerydatatransfer.googleapis.com/mcp
13 shown
Data-source discovery3
list_data_sourcesreadget_data_sourcereadcheck_valid_credsread
Transfer configurations5
create_transfer_configconsequential writeupdate_transfer_configconsequential writedelete_transfer_configconsequential writeget_transfer_configreadlist_transfer_configsread
Transfer runs and logs5
start_manual_transfer_runsconsequential writelist_transfer_runsreadget_transfer_runreaddelete_transfer_runconsequential writelist_transfer_logsread

First-party MCP tool catalog

5 named MCP tools · BigQuery Migration managed MCP server

The exact tools published for the separate bigquerymigration.googleapis.com/mcp endpoint. Reviewed Jul 10, 2026. These tools produce or retrieve translations and DDL suggestions; they do not execute the suggested DDL against a BigQuery dataset. Google OAuth, IAM, quotas, and migration-service availability still apply.

First-party exact listComplete list on cited pagebigquerymigration.googleapis.com/mcp
Query translation3
translate_querydraftget_translationreadexplain_translationread
DDL suggestions2
generate_ddl_suggestiondraftfetch_ddl_suggestionread

First-party connector catalog

32 named connectors · BigQuery Data Transfer Service supported sources

The named inbound data sources on the first-party BigQuery Data Transfer Service overview, with Preview labels retained in item descriptions. Reviewed Jul 10, 2026. This connector catalog describes managed inbound transfers into BigQuery and is separate from all MCP tool catalogs. The service does not transfer data out of BigQuery. Availability, authentication, regions, schedules, pricing, backfill behavior, and data-delivery SLO coverage vary by source; Preview labels are time-sensitive.

First-party exact listVerified partial listBigQuery Data Transfer Service
32 shown
SaaS platforms3
Salesforceread/writeSalesforce Marketing Cloudread/writeServiceNowread/write
Marketing platforms4
Facebook Adsread/writeHubSpotread/writeKlaviyoread/writeMailchimpread/write
Payment and commerce platforms3
PayPalread/writeStriperead/writeShopifyread/write
Databases and data warehouses8
Amazon Redshiftread/writeApache Hive Metastoreread/writeMicrosoft SQL Serverread/writeMySQLread/writeOracleread/writePostgreSQLread/writeSnowflakeread/writeTeradataread/write
Cloud storage3
Cloud Storageread/writeAmazon Simple Storage Service (Amazon S3)read/writeAzure Blob Storageread/write
Google services11
Campaign Managerread/writeComparison Shopping Service (CSS) Centerread/writeDisplay & Video 360read/writeGoogle Adsread/writeGoogle Ad Managerread/writeGoogle Analytics 4read/writeGoogle Merchant Centerread/writeSearch Ads 360read/writeGoogle Playread/writeYouTube Channelread/writeYouTube Content Ownerread/write

Agent access

MCP and adjacent posture

Verified first-party provider MCPGoogle-managed remote MCPCurrent managed service

Role: provider

Read scope: Run SQL queries, retrieve metadata and list BigQuery resources; additional service-specific MCP endpoints exist

Write scope: 8 of 24 reviewed named tools have a write, draft, or mixed action label, including execute_sql, create_transfer_config, update_transfer_config, delete_transfer_config, start_manual_transfer_runs, and others. Read each catalog boundary before enabling them.

Authentication: Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data.

Approval boundary: Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data.

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 access4
UI extensibility3
Portability4
Observability4
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

  • Warehouse-backed campaign and customer-data explorer
  • Marcom control plane
  • Data-quality exception console
  • Approved capability registry
Use in the brief composer →

Multi-platform compositions

  • BigQuery + systems of record: marcom control plane
  • BigQuery + systems of engagement + interface host or builder: 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.

8 recorded sources
MCPRepresentative source
https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp ↗

Official Google Cloud docs confirm remote server enabled with BigQuery API and governed by IAM/OAuth; query execution can incur cost and access sensitive data.

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

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

APISource inventory
https://cloud.google.com/bigquery/docs/reference/rest ↗

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

Publisher updated
May 30, 2026
BYO-UI reviewed
Jul 10, 2026

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

Developer docsSource inventory
https://cloud.google.com/bigquery/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/bigquery ↗

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.

MCP tool catalogTargeted review
BigQuery Migration MCP Reference ↗

Named catalog evidence used on this profile.

Publisher updated
Mar 25, 2026
BYO-UI reviewed
Jul 10, 2026

Targeted first-party catalog 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.