dbt (dbt platform remote MCP) documentation

What it does

The transformation layer of the modern data stack: SQL models, tests and documentation compiled and run against a warehouse, with a hosted "dbt platform" (formerly dbt Cloud) that adds scheduling, a Semantic Layer, a Catalog and a remote MCP server.

Access and connection

MCP support: official

Access requirements: paid - the pricing page lists Developer as free (one seat, "3,000 successful models built per month", with no API access in its feature list), Starter at "$100 per user/month" whose feature list includes "API access", and Enterprise and Enterprise+ at custom pricing; the remote MCP's OAuth path is documented for Starter and above only.

Authentication: oauth (beta) or token. The docs state "OAuth lets you connect to the remote MCP server without copying API tokens into your MCP client" and limit OAuth to "Starter, Enterprise, or Enterprise+" accounts; token auth sends "Authorization: Token YOUR_DBT_ACCESS_TOKEN" (or Bearer) plus an x-dbt-prod-environment-id header, and "If you plan to use execute_sql with token-based auth, you must use a Personal Access Token (PAT)"; "Service tokens do not work for execute_sql".

Research checked: 2026-09-07

These details come from the catalog research. Check the vendor sources below for current setup instructions. They do not establish that a connection or tool call was tested.