@us-all/dbt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DBT_TOOLS | No | Category allowlist, e.g. 'dbt' | |
| DQ_BACKEND | No | bigquery (default) or postgres | bigquery |
| DBT_DISABLE | No | Category denylist, e.g. 'quality' | |
| BQ_PROJECT_ID | No | Explicit BQ project (otherwise inferred from ADC) | |
| MCP_TRANSPORT | No | Set to 'http' to opt in to Streamable HTTP transport | |
| DBT_TARGET_DIR | No | Defaults to $DBT_PROJECT_DIR/target | |
| DQ_SCORE_TABLE | No | FQN of the score-daily table | |
| DBT_ALLOW_WRITE | No | Reserved for future write tools (none in v0.1) | |
| DBT_PROJECT_DIR | Yes | dbt project root (where dbt_project.yml lives) | |
| DQ_RESULTS_TABLE | No | FQN of the checks table (without it, quality category errors at call time) | |
| DBT_RUN_HISTORY_DIR | No | Optional dir for archived run_results.json history | |
| PG_CONNECTION_STRING | No | When DQ_BACKEND=postgres (secret) | |
| GOOGLE_APPLICATION_CREDENTIALS | No | For BigQuery backend (ADC fallback supported) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dbt-list-modelsA | List dbt models from manifest.json with filters (package, tag, materialized, schema, name search) |
| dbt-get-modelA | Get a single dbt model: refs, sources, columns (with catalog types if available), attached tests, raw/compiled SQL |
| dbt-list-testsC | List dbt tests (generic or singular) optionally filtered to a specific model |
| dbt-get-testA | Get a single dbt test: definition, parameters, attached models, latest run result |
| dbt-list-sourcesC | List dbt sources from manifest.json with optional source-group / name filters |
| dbt-get-sourceA | Get a single dbt source: freshness criteria, columns, latest freshness result from sources.json |
| dbt-list-exposuresA | List dbt exposures (downstream BI/ML/application consumers declared in YAML) |
| dbt-list-macrosA | List dbt macros from manifest.json with package / name filters |
| dbt-get-macroA | Get a dbt macro: signature, raw SQL, and reverse-lookup of nodes that call it |
| dbt-list-runsC | List recent dbt invocations from run_results.json files in target/ and DBT_RUN_HISTORY_DIR |
| dbt-get-run-resultsB | Get per-node results from a specific dbt invocation (or the latest run if invocationId omitted) |
| dbt-failed-testsB | Find tests that failed across the last N runs, grouped and ordered by chronic failure count |
| dbt-slow-modelsB | Top N slowest models in a dbt run by execution_time, with bytes_processed when available |
| dbt-coverageA | Per-column test coverage for a dbt model (which columns have tests, table-level tests, coverage %) |
| dbt-graphB | Walk dbt parent_map / child_map to return upstream and downstream nodes (model/source/test) up to a given depth |
| freshness-statusB | Cross-reference dbt source freshness criteria with sources.json results in a single 'is anything stale right now?' answer. |
| incident-contextA | Single asset deep-dive: dbt definition + recent test failures + DQ checks for the dataset. Designed to anchor an LLM-driven incident triage. |
| dbt-sla-statusB | Compare latest dbt run test pass rate and source freshness pass rate against DBT_SLA_CONFIG_PATH thresholds (dbt_sla.test_pass_pct / freshness_pass_pct). Returns per-axis passPct/target/meeting plus caveats when SLA fields or artifacts are missing. |
| dq-list-checksA | List recent rows from DQ_RESULTS_TABLE filtered by dataset / status / type / time window |
| dq-get-check-historyC | Time-series of one check_name's status across the last N days |
| dq-failed-checks-by-datasetB | Group failing checks by dataset across a recent window with the latest 5 failures per dataset |
| dq-score-trendB | Time-series of the 4-axis DQ score (completeness / freshness / validity / anomaly_free) plus overall_score from DQ_SCORE_TABLE |
| dq-tier-statusA | Compare today's overall_score per scope against Tier SLA targets (defaults Tier 1 99.5 / 2 99.0 / 3 95.0; override via DBT_SLA_CONFIG_PATH yaml or DQ_TIER1_TARGET_PCT) and report meeting vs missing counts |
| dq-tier-by-sourceA | Per-tier rollup computed from quality_checks grouped by source. Reads source-to-tier mapping from dbt sources.yml meta.tier and tier targets from DBT_SLA_CONFIG_PATH (falls back to defaults). Reports per-source pass rate, meeting/missing per tier, and untiered sources as caveats. |
| failed-tests-summaryA | Aggregated 24h-ish view: dbt failed tests + DQ checks failures grouped by dataset + most recent failing rows. Replaces 3+ tool calls (dbt-failed-tests + dq-failed-checks-by-dataset + dq-list-checks). |
| dq-score-snapshotA | Aggregated 4-axis score trend + today's Tier compliance + most recent failing checks. Combines dq-score-trend + dq-tier-status + dq-list-checks(fail). |
| search-toolsA | Discover available dbt MCP tools by natural language query across dbt / quality / meta categories. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate-failed-tests | Triage the latest dbt test failures + DQ check failures, group by dataset, infer likely root cause (upstream model error, source freshness, schema drift), and produce a prioritized action list. |
| freshness-degradation-triage | Identify sources/models violating freshness SLAs and rank by Tier impact. If @us-all/airflow-mcp is installed, the prompt also recommends cross-referencing with loading DAG runs. |
| dq-trend-report | Compile a trend report of the 4-axis DQ score over N days, flag regressions vs the prior week, and produce an executive summary. |
| incident-triage | Bundle dbt definition, recent test results, and DQ check results for a single asset into a triage page. If @us-all/airflow-mcp is installed, the prompt instructs the user to also pull DAG run history for full context. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/dbt-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server