Context Layer

The missing context layer for data agents.

Metroflow gives agents business context and approved metric definitions, plus the graph relationships they need to answer accurately.

← All features

Metroflow lineage and context graph
Governed agent context

Three things agents need before they answer

Business knowledge, a query engine, and a headless MCP. All on the same graph.

Business knowledge

How the business talks

Definitions, caveats, policies, and team language live on the same nodes as tables and models.

definitions policies examples owners
Agent query engine

Ask. Plan. Compile SQL.

Agents ask what to measure. Metroflow plans grain, joins, and filters on the graph, then compiles governed SQL.

ask plan compile SQL
MCP-compatible

Headless, lightweight

The same approved graph for Claude Code, Codex, Cursor, and custom MCP agents. No extra control plane.

Claude Code Codex Cursor custom MCP
One source of truth per KPI
Canonical definitions

One source of truth per KPI

MRR and churn as first-class objects with grain, owners, and lineage. Not a SQL snippet lost in a BI folder. Certification: draft → reviewed → certified.

MRR Churn Activation Grain Owner
Trust everywhere

Same number. Audit trail. No three-MRR meeting.

Looker, notebooks, agents, and APIs resolve to one certified ID. Gaps get a pipeline explanation, not a spreadsheet hunt.

Standardization

Every tool, one ID

Finance updates a filter once. Every surface syncs. Rogue dashboard SQL gets flagged.

End metric drift

Stop dueling SQL

Product, finance, and BI stop shipping three versions of MRR. Side-by-side diff when they diverge.

Reconciliation

Audit-ready trails

Certified MRR vs Stripe and CRM. Brain ties the delta to an event on the graph.

On the graph

If it is not a node, the agent cannot invent it

Citations go back to graph nodes. Policies travel with the metric. MCP agents, Workspace, and BI all read the same Context Layer.

See how agents use it →