MCP Gateway · Claude Code
Connect dbt Cloud to Claude Code
Analytics engineers working in the terminal can ask Claude Code about the dbt Cloud project behind their models: lineage, test results, source freshness and compiled SQL. Through the Speakeasy MCP Gateway, dbt Cloud sits behind one governed URL, agents never hold a dbt Cloud credential, and agent hooks check every prompt and tool call before Claude Code runs it.
- Category
- Data & analytics
- Tools
- 24
- Authentication
- API key
- Claude Code
- CLI
Behind the MCP Gateway
Run dbt Cloud MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every dbt Cloud call inspected and logged.
Set up
Add dbt Cloud to Claude Code in 4 steps
- 01
Add dbt Cloud from the catalog
An admin finds dbt Cloud in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
dbt Cloud authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use dbt Cloud
Give teams the
mcp:connectscope on the dbt Cloud server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds dbt Cloud to their gateway on the next call, and removing it takes it away. - 03
Connect Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use dbt Cloud from Claude Code
The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, dbt Cloud's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with dbt Cloud
Trace lineage before editing a model
Before changing a dbt model, Claude Code lists the models it depends on and the downstream ones that depend on it, so you know what the change could break.
Check model health after a failed run
When a run fails, Claude Code checks the model's last run, last test status and upstream data, then reads the details of the failing test.
Read the compiled SQL
Ask for a model's compiled SQL and column details to see exactly what runs in the warehouse, alongside the Jinja you're editing locally.
Tools
24 tools
Each dbt Cloud tool can be allowed or denied per team and role at the MCP Gateway before Claude Code sees it.
get_mart_models
Get the name and description of all mart models in the environment. A mart model is part of the presentation layer of the dbt project. It's where cleaned, transformed data is organized for consumption by end-users, like analysts, dashboards, or business tools.
get_all_models
Get the name and description of all dbt models in the environment.
get_model_details
Retrieves information about a specific dbt model, including compiled SQL, description, database, schema, alias, and column details.
get_model_parents
Retrieves the parent models of a specific dbt model. These are the models that the specified model depends on.
get_model_children
Retrieves the child models (downstream dependencies) of a specific dbt model. These are the models that depend on the specified model.
get_model_health
Retrieves information about the health of a dbt model, including the last time it ran, the last test execution status, and whether the upstream data for the model is fresh.
Control
What Speakeasy can see and stop in Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.
Tool logs
Gateway
Every dbt Cloud call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the dbt Cloud tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to dbt Cloud can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can I stop Claude Code from running SQL against the warehouse?
Does dbt Cloud work in Claude Code on the web?
How do Claude Code users get dbt Cloud?
Are dbt Cloud calls from Claude Code logged?
Connect more