BigQuery MCP server: what an AI agent can query, and the guardrails it needs
Google's BigQuery MCP server gives an agent 9 tools, SQL on raw tables and up to 3,000 rows. It has no per-query byte cap and no metric definitions.
Precisian technical blog — AI-powered data integrity
Google's BigQuery MCP server gives an agent 9 tools, SQL on raw tables and up to 3,000 rows. It has no per-query byte cap and no metric definitions.
Nine ecommerce KPIs, each with its formula and the choice that moves the number: gross or net, shipping, tax, cancellations and attribution window.
Fivetran bills each connection by monthly active rows. On Standard, the first million MAR costs $500 a month at list price, and the rate falls per connection.
An MCP gateway centralizes auth, call logging and rate limits for AI agents. It can't decide what a metric means. That lives in the semantic layer.
MCP Inspector proves your server speaks the protocol, not that its answers are right. The rest: a scrubbed copy, an answer key, scope and cost checks.
MCP doesn't replace your API; most MCP servers call one. What changes is who writes the call: a developer at build time, or a model at runtime.
The Snowflake-managed MCP server exposes only the tools you declare. Answer quality still depends on a semantic view your team writes and maintains.
GA4 reads nine UTM parameters and treats values as case-sensitive text. Without one written convention, a single campaign splits across report rows.
gclid is the Google Ads click ID. It arrives in the URL, lives in a cookie on your domain, and only reaches Google again if you store it with the order.
Windsor.ai starts at $19 a month but caches data for about three weeks. Nine alternatives scored on seven criteria, with when to stay put.
A ranking of 15 AI tools for data analysis on criteria C1 to C7. Ten of the 14 competitors need a data warehouse you have already built.
13 CDPs and Precisian scored on seven data criteria. None of the 13 documents versioned, customer-approved metrics. Activation is where CDPs win.
Nine ETL tools and Precisian scored on seven criteria. None of the nine documents versioned, customer-approved metrics; most leave modeling to you.
For a US Shopify brand, Triple Whale is usually the right call. Precisian serves e-commerce in Brazil, so it's the alternative only if you operate there.
15 Triple Whale alternatives ranked on seven criteria: data isolation, versioned metrics, MCP access, sources, who runs the data, and data ownership.
Cohorts, segments and LTV all come from a pseudonymous ID. An agent almost never needs a name, email, phone number or address to answer them.
No console lists every AI agent touching your data. An MCP permission inventory needs seven columns and a monthly and quarterly review.
ctwa_clid is the click ID of a Click-to-WhatsApp ad. It arrives once, in a webhook, and only attributes a sale if you store it with the order.
Data governance records who decides what about each dataset. For ecommerce, the useful minimum is five records: owner, definition, access, retention, change.
Data lineage maps a number from source to report. dbt's column-level lineage shows the columns, but not the filter that changed the result.
First-party data is what you record in a direct relationship with your customer. Modeled conversions and platform audiences look like it and aren't.
A data dictionary records each metric's name, definition, source, owner, formula and exclusions. A 4 KB definitions file lifted AI accuracy 17 to 23 points.
Write the agent audit log on the server that runs the query. MCP logging was deprecated in the 2026-07-28 spec and was never built for audit.
The Conversions API sends Meta the events your server recorded. Without a Pixel-matching event_id inside 48 hours, one purchase counts twice.
When one agent serves many tenants, data rarely leaks through an attack. It leaks via leftover context, a cache keyed without the tenant, or one shared token.
AI data governance decides what a model may read, not just who may use it. Five questions cover it: scope, isolation, retention, audit trail, metrics.
ChatGPT data analysis is safe for exploring a spreadsheet and unsafe for deciding with it: the math is right, the revenue definition is a guess.
A composable CDP activates customer profiles that live in your warehouse. A data lake keeps every source for analysis. One sends, the other explains.
A lake keeps raw data, a warehouse keeps modeled data, a lakehouse puts transactions on open files. None of them defines net revenue.
Fivetran bills per monthly active row and Airbyte by credit, but in Airbyte Cloud only 67 of 573 source connectors are maintained by Airbyte itself.
Google's Ads MCP server reads your account through GAQL, read-only. It reports what Google logged as a conversion, not shipped orders, Amazon sales or returns.
The Google Analytics MCP server reads GA4 through the Data API, which follows your reporting identity. On Blended, the numbers arrive already modeled.
The query that runs is the worst case of text-to-SQL: the wrong revenue column, the wrong window or a fan-out join returns a clean number and no error.
LTV:CAC divides the margin a customer returns by what it cost to win them. Selling on Amazon hides repeat buyers and platform data shrinks CAC.
Google's Ads MCP server is read-only, yet its OAuth scope can edit and delete your account. For ad data, MCP risk lives in the token's scope.
MER divides total booked revenue by total marketing spend; ROAS divides platform-attributed revenue by one platform's spend. Formulas and limits.
Meta's official Ads MCP server entered open beta on April 29, 2026 with 91 tools. The conversions it reports are the ones Meta attributes to itself.
Shopify's official MCP servers act for buyers, customers and developers. None answers a merchant's margin-by-channel question; community servers fill that gap.
Windsor.ai, Funnel and Improvado all ship MCP servers now. Choose a Supermetrics alternative by who defines the metric, not by connector count.
Google Ads counts purchases 30 days after a click; Meta, 7 days after a click or 1 after a view. Plug all three MCPs into Claude and one order counts twice.
S3 storage is US$ 0.023 per GB-month from a published table. The managed side documents the model and not the rate.
Mollie says it plainly: the customer may not return. Your purchase event lives on the page they never reached.
Chrome still enables them by default. Safari and Firefox blocked years ago. The replacement programme was wound down.
The webhook hands you the ad ID, not the campaign. And the person identifier has no equivalent on the web side.
The chat transcript records what was said, not what was true. Lineage links an answer to the definition and data behind it.
Google lists BigQuery export among features that do not support behavioural modelling. The interface estimates; the export observes.
Amazon's own schema returns 28 traffic fields per product and zero origin fields. The absence is in the schema, not your integration.
GA4's BigQuery export caps at 1 million events a day, and an exceeded export pauses without reprocessing previous days.
One stores and computes; the other defines what is being computed. There is no NOT NULL for semantics.
On a benchmark that prices wrong SQL, abstaining from everything scores 50% and the best real systems score 29.8% to 54.5%.
GA4 has 5 roles and 2 data restrictions, one hiding revenue. The market default is to grant Administrator anyway.
Airflow documents it in one line: if the run never finishes, the SLA is never checked. That is the easy version.
Preemptive item disapproval disapproves what Google suspects, not only what it checked. And GTIN is not required; brand is.
GA4 standard allows 2 or 14 months, and large properties get 2. The aggregate report survives; the exploration does not.
A dashboard answers the question already asked; an MCP server answers the one nobody anticipated. Both read the same definition.
Adobe says it plainly: the two should not match in almost every case. GA4 excludes tax and shipping; Shopify includes both.
The Omie order returns neither CPF nor CNPJ, and in Olist the field called origin is not the marketplace: it means point of sale.
Amazon documents its buyer email as anonymized, and no order carries a traffic source. Cross-channel identity is absent by design.
The spec makes tools model-controlled and tool annotations untrusted. Your tool surface is the security boundary.
A Google Ads campaign name takes 256 characters with no documented content validation. Meta documents no maximum at all.
Access, definition, freshness and provenance, decided before the question. Connection is solved; trust is what nobody shipped.
Fivetran's own FAQ answers 'Do I need MCP?' with 'No. MCP is one option.' They are layers, not rivals. The real difference is governance.
MCP makes authorization optional, and 40.55% of live remote servers expose tools with none. Safety is what you add on top.
Google promises full durability on a subdomain. WebKit caps CNAME-resolved subdomain cookies at seven days. Both are current.
Both numbers are right. The accounting standard recognises revenue on transfer of control; marketing measures at checkout.
Google documents that other platforms take full credit for a conversion with other touchpoints. Nobody deduplicates across vendors.
A data contract declares shape, guarantees and meaning. On Snowflake, BigQuery and Redshift, a declared primary key is enforced by nobody.
Row-level security fails at the role the agent connects with. Per-tenant isolation moves the boundary out of application code and into architecture.
To send customer data to an LLM outside Brazil there are two live legal paths, not three. Global corporate rules are not one of them.
An AI agent can scan your whole warehouse without breaking a rule. Adding a LIMIT does not reduce what you are billed on non-clustered tables.
A semantic layer is where your metric definitions live in a form a machine reads before it computes. Not a tool: a set of written decisions.
Metric hallucination is AI computing correctly on a definition nobody wrote down. Supplying the definition raised accuracy from 45.5% to 67.7%.
Dashboard shows 5x ROI but the cash doesn't add up? Find the hidden costs and non-incremental sales that turn profit into an illusion.
Regional holdout is the only test that separates an MMM that found real signal from one that memorized noise. Learn to design and run it.
Our first article explains what to expect from the Precisian blog: technical insights on GA4, data quality, attribution, and analytics engineering.
Leave your details and the conversation opens straight in WhatsApp.
Opening WhatsApp...