dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres)
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-us-all-dbt": {
"args": [
"-y",
"@us-all/dbt-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
dbt MCP server — manifest.json, run_results.json, sources.json, catalog.json, plus DQ result tables (BigQuery / Postgres) behind one stdio MCP. Built on @us-all/mcp-toolkit.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@us-all/dbt-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @us-all/dbt-mcp against OSV.dev.
Click any tool to inspect its schema.
investigate-failed-testsWhat's broken in the last 24h? - Triage failed tests workflow
freshness-degradation-triageAre any sources stale? - Tier 1 focus optional source freshness triage
dq-trend-reportGive me a stakeholder-friendly DQ trend report - Data quality trend reporting workflow
incident-triageTriage <model | source> - bundles all signals for incident investigation
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data
Query and manage PostgreSQL databases directly from AI assistants
Manage Supabase projects — databases, auth, storage, and edge functions
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP Security Weekly
Get CVE alerts and security updates for io.github.us-all/dbt and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
dbt MCP server —
manifest.json,run_results.json,sources.json,catalog.json, plus DQ result tables (BigQuery / Postgres) behind one stdio MCP. Built on@us-all/mcp-toolkit.
A read-only window into your dbt project for LLM clients. No dbt run triggering — just deep introspection, run-history analysis, source freshness, per-column test coverage, lineage walks, and (if you have a custom DQ result table) historical check trends and Tier SLA status.
For DAG triggering / run history / log tails, install the companion @us-all/airflow-mcp alongside.
dbt, quality, meta) — 21 primitive tools + 5 aggregations + 1 metaextractFields response projection on high-volume reads# 1. add the MCP server
pnpm add -D @us-all/dbt-mcp
# 2. add the DQ backend you actually use (only if you query custom DQ tables):
pnpm add -D @google-cloud/bigquery # OR
pnpm add -D pg
DBT_PROJECT_DIR=/path/to/dbt-project \
DQ_RESULTS_TABLE=my-project.data_ops.quality_checks \
npx @us-all/dbt-mcp
The server speaks MCP stdio; wire it into Claude Desktop / Cursor / any MCP client. Set MCP_TRANSPORT=http to opt in to Streamable HTTP transport (Bearer auth, /health endpoint).
| Category | Tools | Purpose |
|---|---|---|
dbt | 15 + 3 aggregations | Parse manifest.json / run_results.json / sources.json / catalog.json |
quality | 6 + 2 aggregations | Query quality_checks and quality_score_daily (BQ or PG); per-tier rollup via dq-tier-by-source |
meta | 1 (always on) | search-tools for natural-language tool discovery |
Toggle with DBT_TOOLS=dbt (allowlist) or DBT_DISABLE=quality (denylist).
dbt (15 + 3)dbt-list-models, dbt-get-model, dbt-list-tests, dbt-get-test, dbt-list-sources, dbt-get-source, dbt-list-exposures, dbt-list-macros, dbt-get-macro, dbt-list-runs, dbt-get-run-results, dbt-failed-tests, dbt-slow-models, dbt-coverage, dbt-graph, freshness-status, incident-context, dbt-sla-status
quality (6 + 2)dq-list-checks, dq-get-check-history, dq-failed-checks-by-dataset, dq-score-trend, dq-tier-status, dq-tier-by-source, failed-tests-summary, dq-score-snapshot
| Prompt | Use when |
|---|---|
investigate-failed-tests | "What's broken in the last 24h?" |
freshness-degradation-triage | "Are any sources stale?" (Tier 1 focus optional) |
dq-trend-report | "Give me a stakeholder-friendly DQ trend report" |
incident-triage | "Triage <model | source>" — bundles all signals |
| Env | Required | Notes |
|---|---|---|
DBT_PROJECT_DIR | yes | dbt project root (where dbt_project.yml lives) |
DBT_TARGET_DIR | no | Defaults to $DBT_PROJECT_DIR/target |
DBT_RUN_HISTORY_DIR | no | Optional dir for archived run_results.json history |
DQ_BACKEND | no | bigquery (default) or postgres |
DQ_RESULTS_TABLE | no | FQN of the checks table; required only for checks-based quality tools |
DQ_SCORE_TABLE | no | FQN of the score-daily table; required for score-only tools |
GOOGLE_APPLICATION_CREDENTIALS | no | For BigQuery backend (ADC fallback supported) |
BQ_PROJECT_ID | no | Explicit BQ project (otherwise inferred from ADC) |
PG_CONNECTION_STRING | no | When DQ_BACKEND=postgres (secret) |
DQ_SCHEMA | no | generic (default) or us-all — base schema preset for the quality category |
DQ_COL_* | no | Per-column overrides on top of DQ_SCHEMA (see below). Overrides must be simple SQL identifi |