Does Codex support the Dbt Cloud MCP server?

Yes. Codex connects to the Dbt Cloud MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

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

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

Which Dbt Cloud tools can Codex 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 Codex?

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

What if Codex doesn't show Dbt Cloud tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect Dbt Cloud to Codex (MCP setup guide)

Ask Codex to use the get environment tool in Dbt Cloud
Ask Codex to use the retry failed job tool in Dbt Cloud
Ask Codex to use the list accounts tool in Dbt Cloud
Ask Codex to use the get account tool in Dbt Cloud
Ask Codex to use the list runs 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 the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Dbt Cloud tools.

Once Dbt Cloud is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, 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.

Limit which Dbt Cloud tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single Dbt Cloud tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

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

Does Codex support the Dbt Cloud MCP server?
Yes. Codex connects to the Dbt Cloud MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Dbt Cloud to Codex?
No. You sign in to Dbt Cloud once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Dbt Cloud tools can Codex 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 Codex?
Yes. Role-based access control decides who can use Dbt Cloud and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Dbt Cloud tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.