01 · Records and state owned
Governed models, metrics, lineage, freshness, Semantic Layer, Discovery/Admin APIs, CLI/Fusion, SQL and codegen toolsets
dbt Labs
dbt
Curated anchor platform in analytics engineering and semantic layer with material relevance to the Marcom operating stack and a first-party developer surface.
Automation, data & MCP bridgesSystem of orchestrationAgent-accessible SaaS
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.
02 · Data you can retrieve
Governed models, metrics, lineage, freshness, Semantic Layer, Discovery/Admin APIs, CLI/Fusion, SQL and codegen toolsets
03 · Actions and write paths
The targeted review confirmed this dbt capability surface: Governed models, metrics, lineage, freshness, Semantic Layer, Discovery/Admin APIs, CLI/Fusion, SQL and codegen toolsets. It did not normalize every mutation tool. Treat writes as unapproved until each current tool, scope, plan and approval behavior is verified.
04 · Authentication and permissions
Authentication model is documented by the vendor; inspect the cited source before implementation. Official dbt docs confirm local and remote modes and multiple configurable toolsets; access to private APIs/SQL should be scoped.
05 · Monitoring, approval, and recovery
Official dbt docs confirm local and remote modes and multiple configurable toolsets; access to private APIs/SQL should be scoped. Official dbt docs confirm local and remote modes and multiple configurable toolsets; access to private APIs/SQL should be scoped.
06 · Gaps and implementation limits
Official dbt docs confirm local and remote modes and multiple configurable toolsets; access to private APIs/SQL should be scoped.
First-party access
Documented surfaces
dbt SQL tools ↗dbt documents text-to-SQL and SQL execution in its MCP toolsets. Tool availability differs between local and remote servers and by plan, configured toolsets, connected warehouse authority, dbt permissions, and usage limits; SQL does not imply unrestricted access to every underlying relation.Source: dbt Model Context Protocol serverAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider MCPOfficial local and remote dbt MCPCurrent documented service
Role: provider
Read scope: Governed models, metrics, lineage, freshness, Semantic Layer, Discovery/Admin APIs, CLI/Fusion, SQL and codegen toolsets
Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Official dbt docs confirm local and remote modes and multiple configurable toolsets; access to private APIs/SQL should be scoped.
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 dbt Labs ships these experiences.
Single-platform patterns
- Trusted Marcom metrics and lineage explorer
- Marcom control plane
- Data-quality exception console
- Approved capability registry
Multi-platform compositions
- dbt + systems of record: marcom control plane
- dbt + systems of engagement + interface host or builder: cross-system decision workspace
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.
4 recorded sources
MCPRepresentative source
https://docs.getdbt.com/docs/dbt-ai/about-mcp ↗Official dbt docs confirm local and remote modes and multiple configurable toolsets; access to private APIs/SQL should be scoped.
- Publisher updated
- Jul 9, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://docs.getdbt.com/docs/dbt-cloud-apis/overview ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Jul 9, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.getdbt.com/ ↗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://www.getdbt.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.
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.