MCP Gateway · Cursor
Connect dbt Cloud to Cursor
Writing dbt models in Cursor goes faster when the editor knows the rest of the project. With dbt Cloud behind the Speakeasy MCP Gateway, Cursor can look up similar models, source columns and macro metadata while you write SQL. Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it first, and every hook event carries the user's email.
- Category
- Data & analytics
- Tools
- 24
- Authentication
- API key
- Cursor
- Editor and terminal
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 Cursor 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 Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use dbt Cloud from Cursor
The first time Cursor 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 Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with dbt Cloud
Find a model to reuse
Before writing a new model, Cursor searches the environment for semantically similar ones by name, description and columns, so you reuse a model instead of duplicating it.
Check source columns while writing SQL
Cursor reads a source's schema, column types and freshness status while you write the staging model that selects from it.
Call a project macro correctly
When a model needs one of the project's macros, Cursor fetches the macro's metadata before writing the call, so you don't have to open its file.
Tools
24 tools
Each dbt Cloud tool can be allowed or denied per team and role at the MCP Gateway before Cursor 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 Cursor
The gateway covers every client the same way. The rest depends on what Cursor 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 Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Can Cursor generate SQL with dbt Cloud but not run it?
Do Speakeasy hooks run for Cursor Cloud agents working on dbt?
How do Cursor users get dbt Cloud?
Are dbt Cloud calls from Cursor logged?
Connect more