AgentHubAgentHub

dbt MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.us-all/dbt · v1.0.7

dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres)

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres) dbt is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Required
secret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Setup tutorial

  1. Open the dbt page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add dbt --env DBT_PROJECT_DIR=<DBT_PROJECT_DIR> -- npx -y @us-all/dbt-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "dbt": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/dbt-mcp"
      ],
      "env": {
        "DBT_PROJECT_DIR": "<DBT_PROJECT_DIR>"
      }
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for dbt

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for dbt?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

dbt requires environment variables (DBT_PROJECT_DIR). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "DBT_PROJECT_DIR": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

dbt Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: dbtExecute the core tool interface of dbt
Request ArgumentsJSON Schema
{
  "target": "dbt",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

dbt + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Planning with files

v3.23.0

SkillClawHub44.6k

io.clawhub.othmanadi/planning-with-files

Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.

source

ClawCall

v2.0.1

SkillClawHub53.1k

io.clawhub.clawcall-dev/clawcall-dev

Use when the user wants an AI agent to place a US phone call, call a business, handle hold or phone menus, confirm/reschedule/cancel/book/follow up/check an order, reach a real person, leave voicemail, connect the user into a live call, configure ClawCall voice/personality/profile or inbound reserved-number answering, poll received inbound calls, or link a ClawCall API key. Not for SMS, email, or international calls.

source

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: dbt
HTML
<a href="https://myagenthub.cn/p/io.github.us-all/dbt" title="Listed on AgentHub: dbt" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.us-all/dbt?lang=en" alt="Listed on AgentHub: dbt" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: dbt](https://myagenthub.cn/badge/io.github.us-all/dbt?lang=en)](https://myagenthub.cn/p/io.github.us-all/dbt)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.us-all/dbt",
  "type": "mcp-server",
  "version": "1.0.7",
  "displayName": "dbt",
  "description": "dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres)",
  "repository": {
    "url": "https://github.com/us-all/dbt-mcp-server",
    "source": "github"
  },
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "@us-all/dbt-mcp",
        "version": "1.0.7",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "DBT_PROJECT_DIR",
            "description": "Path to dbt project root (where dbt_project.yml lives).",
            "isRequired": true
          },
          {
            "name": "DBT_TARGET_DIR",
            "description": "dbt target dir for manifest.json/run_results.json (default: $DBT_PROJECT_DIR/target)."
          },
          {
            "name": "DBT_RUN_HISTORY_DIR",
            "description": "Optional dir for archived run_results.json history (glob-scanned)."
          },
          {
            "name": "DQ_BACKEND",
            "description": "DQ result table backend: 'bigquery' (default) or 'postgres'."
          },
          {
            "name": "DQ_RESULTS_TABLE",
            "description": "Fully qualified DQ checks table, e.g. 'project.data_ops.quality_checks'."
          },
          {
            "name": "DQ_SCORE_TABLE",
            "description": "Fully qualified DQ score-daily table, e.g. 'project.data_ops.quality_score_daily'."
          },
          {
            "name": "GOOGLE_APPLICATION_CREDENTIALS",
            "description": "Service account key path for BigQuery (ADC fallback supported)."
          },
          {
            "name": "BQ_PROJECT_ID",
            "description": "Explicit BigQuery project ID for DQ queries."
          },
          {
            "name": "PG_CONNECTION_STRING",
            "description": "Postgres connection string when DQ_BACKEND=postgres.",
            "isSecret": true
          },
          {
            "name": "DBT_ALLOW_WRITE",
            "description": "Reserved for future write tools. Default read-only."
          },
          {
            "name": "DQ_SCHEMA",
            "description": "DQ result-table schema preset: 'generic' (default) or 'us-all'. Use DQ_COL_* env vars to override individual columns on top of the preset."
          },
          {
            "name": "DQ_COL_RUN_AT",
            "description": "Override for the timestamp/date column on the DQ checks table. Default depends on DQ_SCHEMA preset."
          },
          {
            "name": "DQ_COL_CHECK_TYPE",
            "description": "Override for the check-type column on the DQ checks table. Default 'check_type'."
          },
          {
            "name": "DQ_COL_STATUS",
            "description": "Override for the status column on the DQ checks table. Default 'status'."
          },
          {
            "name": "DQ_COL_DATASET",
            "description": "Override for the dataset/source column on the DQ checks table. Default depends on preset."
          },
          {
            "name": "DQ_COL_TABLE_NAME",
            "description": "Override for the table/target-name column on the DQ checks table. Default depends on preset."
          },
          {
            "name": "DQ_COL_SEVERITY",
            "description": "Override for the severity/dimension column on the DQ checks table. Default depends on preset."
          },
          {
            "name": "DQ_COL_FAILURE_COUNT",
            "description": "Override for the numeric failure-count column on the DQ checks table. Default depends on preset."
          },
          {
            "name": "DQ_COL_MESSAGE",
            "description": "Override for the message column on the DQ checks table. Default depends on preset."
          },
          {
            "name": "DQ_COL_CHECK_NAME",
            "description": "Override for the check_name column on the DQ checks table. Set to 'none'/'null'/'-' to synthesize check_name from check_type and table_name."
          },
          {
            "name": "DQ_COL_SCORE_DATE",
            "description": "Override for the date column on the DQ score-daily table. Default depends on preset."
          },
          {
            "name": "DQ_COL_SCOPE",
            "description": "Override for the scope column on the DQ score-daily table. Set to 'none'/'null'/'-' if the table has no per-scope rollup."
          },
          {
            "name": "DQ_COL_TIER",
            "description": "Override for the tier column on the DQ score-daily table. Set to 'none'/'null'/'-' if the table has no tier dimension."
          },
          {
            "name": "DQ_TIER1_TARGET_PCT",
            "description": "When no tier column is configured (us-all preset or DQ_COL_TIER=none), the overall_score threshold dq-tier-status compares against (default 99.5). Superseded by DBT_SLA_CONFIG_PATH tier_sla.1 if both are set."
          },
          {
            "name": "DBT_SLA_CONFIG_PATH",
            "description": "Optional path to a YAML file that defines tier_sla (per-tier overall_score targets) and dbt_sla (test/freshness pass rates). When set, dq-tier-status and dq-tier-by-source read tier targets from this file, and dbt-sla-status compares run_results / sources pass rates against dbt_sla.test_pass_pct / freshness_pass_pct. Mtime cached."
          },
          {
            "name": "DBT_TOOLS",
            "description": "Comma-separated category allowlist (dbt,quality,meta)."
          },
          {
            "name": "DBT_DISABLE",
            "description": "Comma-separated category disablelist."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.us-all/dbt",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.us-all%2Fdbt/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}
dbt MCP Setup & Guide - AgentHub