MCP Gateway · Claude
Connect dbt Cloud to Claude
People outside the data team often need a metric but can't write SQL or don't know which table to trust. Once dbt Cloud is reachable from Claude, they can query the dbt Semantic Layer in plain language and get answers built on definitions the data team maintains. The gateway decides which dbt Cloud tools each role may call.
- Category
- Data & analytics
- Tools
- 24
- Authentication
- API key
- Claude
- Web, desktop and mobile
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 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
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use dbt Cloud from Claude
The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with dbt Cloud
Get a metric without writing SQL
Ask Claude for a metric, such as revenue by month, and it queries the dbt Semantic Layer to answer from your warehouse.
Learn how a metric can be split
Before quoting a number in a deck or email, ask Claude which metrics exist and which dimensions each one can be broken down by.
Check whether a report is stale
If a report looks out of date, ask Claude whether the model behind it ran recently and passed its tests, before raising it with the data team.
Tools
24 tools
Each dbt Cloud tool can be allowed or denied per team and role at the MCP Gateway before Claude 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
The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can business users in Claude run arbitrary SQL through dbt Cloud?
Are Claude conversations about dbt data reviewable?
How do Claude users get dbt Cloud?
Are dbt Cloud calls from Claude logged?
Connect more