dbt anchors governed analytics access because its MCP can expose models, metrics, lineage, freshness, Semantic Layer queries, metadata, and SQL, while the self-hosted mode can also place dbt CLI and code-generation workflows behind an agent interface.
Concrete capability record
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.
dbt models, metrics, lineage, freshness, job artifacts, Semantic Layer data, Discovery and Administrative API resources, SQL results, Fusion tools, and, in self-hosted mode, local projects, CLI commands, and Codegen outputs.
Remote and self-hosted tools can query authorized Semantic Layer data, metadata, lineage, freshness, job results, Discovery/Admin API resources, and SQL results; exact availability follows the dbt plan and enabled tools.
The self-hosted server can run dbt CLI commands such as `dbt run`, `dbt build`, and `dbt test` and use Codegen against local projects; remote MCP does not support local CLI or project authoring. SQL, Administrative API, and Fusion tools must be assessed individually rather than presumed read-only.
Remote MCP supports OAuth or PAT/service-token headers. Token access requires Semantic Layer and Developer permissions; `execute_sql` requires a PAT plus development-environment and user IDs. Remote OAuth is public beta for Starter, Enterprise, and Enterprise+ accounts and presents consent scopes that users may approve or deny.
dbt lets operators choose remote consumption versus self-hosted development, disable self-hosted toolsets, and approve or deny OAuth scopes. The MCP server does not retain production data or job results; source retention follows dbt platform. BYO-UI should show server mode and tool identity before executing SQL, Admin, Fusion, or CLI actions.
Remote MCP has no local CLI or project access, and underlying tools vary by plan. Its default global limit is 5,000 requests per minute per IP; exhausting dbt Copilot actions blocks all remote MCP tools until reset. Remote OAuth is public beta on Starter, Enterprise, and Enterprise+, while token use has separate permission and header requirements.
First-party access
Agent access
Support: Official MCP server
Read scope: Query governed metrics and Semantic Layer data, inspect models/metadata/lineage/freshness and job results, and use authorized Discovery, Administrative, SQL, and Fusion read capabilities.
Write scope: Self-hosted MCP can execute local dbt CLI and Codegen workflows; remote MCP excludes those workflows. Do not classify SQL, Administrative API, or Fusion tools as harmless reads until the selected tool and warehouse/platform permission are verified.
Authentication: Remote HTTP MCP uses OAuth or an Authorization header carrying a PAT or service token; self-hosted MCP runs locally through `uvx dbt-mcp` and can optionally connect to dbt platform APIs.
Approval boundary: dbt OAuth provides scope consent, but the reviewed docs do not establish per-command human approval for SQL, Admin, Fusion, or self-hosted CLI execution. A BYO-UI should require explicit confirmation for commands that build models, execute SQL, change administrative state, or affect a production warehouse.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that dbt Labs ships them.
Evidence and dates
“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.
Self-hosted/remote split, tool categories, plan gating, authentication, limits, and retention
MCP mode, tool, plan, rate-limit, Copilot-allotment, and retention review completed 2026-07-22
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
remote MCP use cases, credentials, environment context, OAuth consent, and plan/beta boundaries
remote MCP use cases, credentials, environment context, OAuth consent, and plan/beta boundaries reviewed from live first-party documentation on 2026-07-22.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
