MCP Gateway · Claude Cowork
Connect dbt Cloud to Claude Cowork
Some dbt Cloud jobs are long: documenting every model in a project, or building a monthly metrics pack with the SQL behind each figure. Cowork can run them step by step, reaching dbt Cloud through the Speakeasy MCP Gateway. Speakeasy can deny a prompt before its step starts, and every Cowork session is attributed to the person who started it.
- Category
- Data & analytics
- Tools
- 24
- Authentication
- API key
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the dbt Cloud server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use dbt Cloud from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with dbt Cloud
Write a guide to the dbt project
Cowork goes through every model in the environment, reads its description, columns and parents, and writes a plain-language guide for new analysts.
Build the monthly metrics pack
Cowork queries each metric for the month, writes the commentary and appends the compiled SQL behind each figure so finance can trace it.
Audit source freshness
Cowork works source by source, checks the freshness status of each one, and lists the sources that are behind for 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 Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Can Cowork tasks reach dbt Cloud from personal Claude accounts?
When does Cowork pick up a change to the dbt Cloud plugin?
How do Claude Cowork users get dbt Cloud?
Are dbt Cloud calls from Claude Cowork logged?
Connect more