dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres)
To add dbt to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 27 environment variables, listed below.
Install
npx -y @us-all/dbt-mcp@1.0.7Environment variables
DBT_PROJECT_DIRSet in your MCP configDBT_TARGET_DIRSet in your MCP configDBT_RUN_HISTORY_DIRSet in your MCP configDQ_BACKENDSet in your MCP configDQ_RESULTS_TABLESet in your MCP configDQ_SCORE_TABLESet in your MCP configGOOGLE_APPLICATION_CREDENTIALSSet in your MCP configBQ_PROJECT_IDSet in your MCP configPG_CONNECTION_STRINGSet in your MCP configDBT_ALLOW_WRITESet in your MCP configDQ_SCHEMASet in your MCP configDQ_COL_RUN_ATSet in your MCP configDQ_COL_CHECK_TYPESet in your MCP configDQ_COL_STATUSSet in your MCP configDQ_COL_DATASETSet in your MCP configDQ_COL_TABLE_NAMESet in your MCP configDQ_COL_SEVERITYSet in your MCP configDQ_COL_FAILURE_COUNTSet in your MCP configDQ_COL_MESSAGESet in your MCP configDQ_COL_CHECK_NAMESet in your MCP configDQ_COL_SCORE_DATESet in your MCP configDQ_COL_SCOPESet in your MCP configDQ_COL_TIERSet in your MCP configDQ_TIER1_TARGET_PCTSet in your MCP configDBT_SLA_CONFIG_PATHSet in your MCP configDBT_TOOLSSet in your MCP configDBT_DISABLESet in your MCP configInstall with your client
claude mcp add dbt --env DBT_PROJECT_DIR=<YOUR_DBT_PROJECT_DIR> --env DBT_TARGET_DIR=<YOUR_DBT_TARGET_DIR> --env DBT_RUN_HISTORY_DIR=<YOUR_DBT_RUN_HISTORY_DIR> --env DQ_BACKEND=<YOUR_DQ_BACKEND> --env DQ_RESULTS_TABLE=<YOUR_DQ_RESULTS_TABLE> --env DQ_SCORE_TABLE=<YOUR_DQ_SCORE_TABLE> --env GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS> --env BQ_PROJECT_ID=<YOUR_BQ_PROJECT_ID> --env PG_CONNECTION_STRING=<YOUR_PG_CONNECTION_STRING> --env DBT_ALLOW_WRITE=<YOUR_DBT_ALLOW_WRITE> --env DQ_SCHEMA=<YOUR_DQ_SCHEMA> --env DQ_COL_RUN_AT=<YOUR_DQ_COL_RUN_AT> --env DQ_COL_CHECK_TYPE=<YOUR_DQ_COL_CHECK_TYPE> --env DQ_COL_STATUS=<YOUR_DQ_COL_STATUS> --env DQ_COL_DATASET=<YOUR_DQ_COL_DATASET> --env DQ_COL_TABLE_NAME=<YOUR_DQ_COL_TABLE_NAME> --env DQ_COL_SEVERITY=<YOUR_DQ_COL_SEVERITY> --env DQ_COL_FAILURE_COUNT=<YOUR_DQ_COL_FAILURE_COUNT> --env DQ_COL_MESSAGE=<YOUR_DQ_COL_MESSAGE> --env DQ_COL_CHECK_NAME=<YOUR_DQ_COL_CHECK_NAME> --env DQ_COL_SCORE_DATE=<YOUR_DQ_COL_SCORE_DATE> --env DQ_COL_SCOPE=<YOUR_DQ_COL_SCOPE> --env DQ_COL_TIER=<YOUR_DQ_COL_TIER> --env DQ_TIER1_TARGET_PCT=<YOUR_DQ_TIER1_TARGET_PCT> --env DBT_SLA_CONFIG_PATH=<YOUR_DBT_SLA_CONFIG_PATH> --env DBT_TOOLS=<YOUR_DBT_TOOLS> --env DBT_DISABLE=<YOUR_DBT_DISABLE> -- npx -y @us-all/dbt-mcp@1.0.7
Run this in a terminal to add the server to Claude Code.
What this does
dbt exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
DBT_PROJECT_DIR DBT_TARGET_DIR DBT_RUN_HISTORY_DIR DQ_BACKEND DQ_RESULTS_TABLE DQ_SCORE_TABLE GOOGLE_APPLICATION_CREDENTIALS BQ_PROJECT_ID PG_CONNECTION_STRING DBT_ALLOW_WRITE DQ_SCHEMA DQ_COL_RUN_AT DQ_COL_CHECK_TYPE DQ_COL_STATUS DQ_COL_DATASET DQ_COL_TABLE_NAME DQ_COL_SEVERITY DQ_COL_FAILURE_COUNT DQ_COL_MESSAGE DQ_COL_CHECK_NAME DQ_COL_SCORE_DATE DQ_COL_SCOPE DQ_COL_TIER DQ_TIER1_TARGET_PCT DBT_SLA_CONFIG_PATH DBT_TOOLS DBT_DISABLE
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install dbt?
Run the Claude Code command in the install section to add dbt to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with dbt?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to dbt as well.
Does dbt need an API key?
Yes. Before it can run, set these environment variables: DBT_PROJECT_DIR, DBT_TARGET_DIR, DBT_RUN_HISTORY_DIR, DQ_BACKEND, DQ_RESULTS_TABLE, DQ_SCORE_TABLE, GOOGLE_APPLICATION_CREDENTIALS, BQ_PROJECT_ID, PG_CONNECTION_STRING, DBT_ALLOW_WRITE, DQ_SCHEMA, DQ_COL_RUN_AT, DQ_COL_CHECK_TYPE, DQ_COL_STATUS, DQ_COL_DATASET, DQ_COL_TABLE_NAME, DQ_COL_SEVERITY, DQ_COL_FAILURE_COUNT, DQ_COL_MESSAGE, DQ_COL_CHECK_NAME, DQ_COL_SCORE_DATE, DQ_COL_SCOPE, DQ_COL_TIER, DQ_TIER1_TARGET_PCT, DBT_SLA_CONFIG_PATH, DBT_TOOLS, DBT_DISABLE. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-us-all-dbt)<a href="https://clauderules.net/mcp/io-github-us-all-dbt" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-us-all-dbt" alt="Listed on clauderules.net" /></a>More Database MCP servers
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.