Capability
- user-invocable
- false
- metadata
{
"author": "dbt-labs"
}
Topics
- MCP
- API
- dbt
- configuration
- claude
- cursor
- vscode
- authentication
- semantic-layer
What it does
Generates MCP server configuration JSON for dbt, handles credential setup, and validates connectivity across local and remote server types for Claude Desktop, Claude Code, Cursor, and VS Code. Use this when installing or troubleshooting the dbt MCP server to enable AI agents to access the dbt CLI, Semantic Layer, Discovery API, and Admin API.
Generated from the current SKILL.md.
Frequently asked
Does this skill work with Claude Desktop, Cursor, and VS Code?
Yes. The skill provides client-specific setup instructions for Claude Desktop, Claude Code, Cursor, and VS Code, with different configuration paths and formats for each.
What is the difference between local and remote dbt MCP server?
Local server runs via `uvx` on your machine and supports CLI commands (run, build, test) plus platform features if you add credentials. Remote server connects via HTTP to dbt Cloud and handles consumption only (querying metrics, exploring metadata) without CLI access.
Do I need a dbt Cloud account to use this skill?
Not for local CLI-only setups. A dbt Cloud account is required only if you want platform features (Semantic Layer, Discovery API, Admin API) or if you use the remote server.
How should I store sensitive credentials like tokens?
Use environment variable references (e.g., `${DBT_TOKEN}`) in config files instead of literal values, store tokens in `.env` files added to `.gitignore`, and never commit or log token values.
Can I enable SQL and codegen tools?
Yes, but they are disabled by default. Set `DISABLE_SQL=false` or `DISABLE_DBT_CODEGEN=false` as environment variables to enable them.
Generated from the current SKILL.md. These answers refresh after source changes.