Does Cursor support the Dbt Cloud MCP server?

Yes. Cursor connects to the Dbt Cloud MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.

Do I need an API key to connect Dbt Cloud to Cursor?

No. You sign in to Dbt Cloud once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.

Which Dbt Cloud tools can Cursor use?

All 23 Dbt Cloud tools your team allows, such as Get Account, List Runs, List Projects. Admins can narrow that list per team.

Can I control which teammates use Dbt Cloud in Cursor?

Yes. Role-based access control decides who can use Dbt Cloud and which of its tools appear in Cursor, and every call is logged with the person's identity.

What if Cursor doesn't show Dbt Cloud tools?

Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.

Connect Dbt Cloud to Cursor (MCP setup guide)

Ask Cursor to use the get run tool in Dbt Cloud
Ask Cursor to use the trigger job run tool in Dbt Cloud
Ask Cursor to use the list webhooks tool in Dbt Cloud
Ask Cursor to use the get run failure details tool in Dbt Cloud
Ask Cursor to use the get webhook tool in Dbt Cloud

1. Enable Dbt Cloud in Metorial
In your Metorial portal, enable the Dbt Cloud MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add Metorial to your MCP config
Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
```
{
  "mcpServers": {
    "metorial": {
      "url": "<your-magic-mcp-url>"
    }
  }
}
```
3. Sign in
Open Customize in the sidebar, find Metorial and sign in to load Dbt Cloud tools.

Once Dbt Cloud is enabled in Metorial, teammates sign in with SSO and get the same connection in Cursor, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Get Account: Retrieve details about the configured dbt Cloud account.
List Runs: List dbt Cloud job runs with optional filters for job, project, environment, or status.
List Projects: List all projects in the dbt Cloud account.
List Users: List all users in the dbt Cloud account.
Manage Webhook: Create, update, or delete a dbt Cloud webhook subscription.
List Environments: List all environments for a given dbt Cloud project.
Get Run Artifact: Fetch an artifact file from a completed dbt Cloud run as a Slate attachment.
Cancel Run: Cancel a currently queued or in-progress dbt Cloud job run.
List Jobs: List dbt Cloud jobs, optionally filtered by project or environment.
Get Job: Retrieve detailed information about a specific dbt Cloud job, including its schedule, execution steps, settings, and run history metadata.
Get Run: Retrieve detailed information about a specific dbt Cloud job run.
Trigger Job Run: Trigger a new run for a dbt Cloud job.
List Webhooks: List dbt Cloud webhook subscriptions configured for the account.
Get Run Failure Details: Retrieve retry-related failure details for a failed dbt Cloud run, including the failed step and skipped steps when available.
Get Webhook: Retrieve a dbt Cloud webhook subscription by ID, including subscribed events, target URL, active state, and scoped job IDs when available.
And 8 more on the Dbt Cloud MCP server page.

Cursor picks MCP tools automatically when they are relevant, including in Plan Mode. Name a Dbt Cloud tool to steer it.
Cursor asks for approval before it uses an MCP tool by default. Click the arrow next to the tool name to check the arguments first.
Switch the Metorial server off from Customize in the sidebar without removing it.
Cursor shows each Dbt Cloud tool response in chat, with expandable views of the arguments and the result.

Metorial connects but tools are missing or failing: Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.
Your company blocks the server: Enterprise admins approve remote servers in Team Settings, then MCP Configuration. Ask them to add a URL entry for your Metorial URL.
Cursor asks before every tool call: That is the default. Allowlist the Metorial tools you trust in your Run Mode settings to run them without a prompt.

Based on the Cursor MCP documentation.

Frequently asked questions

Common questions about connecting Dbt Cloud to AI agents with Metorial.

Does Cursor support the Dbt Cloud MCP server?
Yes. Cursor connects to the Dbt Cloud MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.
Do I need an API key to connect Dbt Cloud to Cursor?
No. You sign in to Dbt Cloud once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.
Which Dbt Cloud tools can Cursor use?
All 23 Dbt Cloud tools your team allows, such as Get Account, List Runs, List Projects. Admins can narrow that list per team.
Can I control which teammates use Dbt Cloud in Cursor?
Yes. Role-based access control decides who can use Dbt Cloud and which of its tools appear in Cursor, and every call is logged with the person's identity.
What if Cursor doesn't show Dbt Cloud tools?
Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.