All skills
dbt-labs avatar

/configuring-dbt-mcp-server

@faadc25 official
by dbt Labsdbt-labs/dbt-agent-skills729 stars
62

Generates MCP server configuration JSON, resolves authentication setup, and validates server connectivity for dbt. Use when setting up, configuring, or troubleshooting the dbt MCP server for AI tools like Claude Desktop, Claude Code, Cursor, or VS Code.

Use this Skill: https://skilld.dev/gh/dbt-labs/dbt-agent-skills/configuring-dbt-mcp-server

This session only. Nothing lands on disk.

referencesfinding-credentials.md

≈693 tokens on demand. Your agent reads this file only when SKILL.md points to it.

How to Find Your Credentials

Which Token Type Should I Use?

Use Case Token Type Why
Personal development setup Personal Access Token (PAT) Inherits your permissions, works with all APIs including execute_sql
Shared team setup Service Token Multiple users, controlled permissions, separate from individual accounts
Using execute_sql tool PAT (required) SQL tools that require x-dbt-user-id need a PAT
CI/CD or automation Service Token System-level access, not tied to a person

Personal Access Token (PAT)

  1. Go to Account Settings → expand API tokens → click Personal tokens
  2. Click Create personal access token
  3. Enter a descriptive name and click Save
  4. Copy the token immediately — it won't be shown again

Notes:

  • Requires a Developer license
  • Inherits all permissions from your user account
  • Account-scoped: create separate tokens for each dbt account you access
  • Rotate regularly for security

Service Token

Use service tokens for system-level integrations (CI/CD, automation) rather than user-specific access.

  1. Go to Account Settings → Service Tokens (in left sidebar)
  2. Click + New Token
  3. Select the appropriate permission set for your use case
  4. Save the token immediately — it won't be shown again

Permission sets for MCP:

  • Semantic Layer Only: For querying metrics only
  • Metadata Only: For Discovery API access
  • Job Admin: For Admin API (triggering jobs)
  • Developer: For broader access

Notes:

  • Requires Developer license + account admin permissions to create
  • Service tokens belong to the account, not a user
  • Cannot use service tokens for execute_sql — use PAT instead

Account ID

  1. Sign in to dbt Cloud
  2. Look at the URL in your browser — the Account ID is the number after /accounts/

Example: In https://cloud.getdbt.com/settings/accounts/12345/..., the Account ID is 12345

Alternative: Go to Settings → Account Settings and check the URL.

Environment ID (Production or Development)

  1. In dbt Cloud, go to Deploy → Environments
  2. Click on the environment (Production or Development)
  3. Look at the URL — the Environment ID is the last number

URL pattern: https://cloud.getdbt.com/deploy/<account_id>/projects/<project_id>/environments/<environment_id>

Example: In .../environments/98765, the Environment ID is 98765

User ID

  1. Go to Account Settings → Team → Users
  2. Click on your user profile
  3. Look at the URL — the number after /users/ is your User ID

Example: In https://cloud.getdbt.com/settings/accounts/12345/users/67891, the User ID is 67891

Source: SKILL.md on GitHub

1 warning17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill provides instructions and configuration templates for setting up the dbt Model Context Protocol (MCP) server. It emphasizes security best practices for credential management and uses standard tools from dbt-labs.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer6mo

    3/4 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at faadc25. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 7 months ago
user-invocable
false
metadata
{
  "author": "dbt-labs"
}
  • MCP
  • API
  • dbt
  • configuration
  • claude
  • cursor
  • vscode
  • authentication
  • semantic-layer

README badge

README badge for dbt-labs/dbt-agent-skills/configuring-dbt-mcp-server

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.

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.