Schema | dbt-mcp

dbt-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`BQ_PROJECT`	No	BigQuery project
`BQ_LOCATION`	No	BigQuery location
`DBT_TARGET_DIR`	Yes	dbt target/ directory (required)
`DBT_DUCKDB_PATH`	No	DuckDB warehouse file

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
run_summaryA	Summarise the most recent dbt run: how many tests failed, and their names. `Use this first to judge overall health before drilling into any one failure.`
list_failing_testsA	List every failing test in the last dbt run, with what it guards. `Returns the test name, the model and column it protects, how many rows failed, and whether it is a generic (not_null, unique...) or hand-written test.`
sample_failing_rowsA	Fetch the actual rows that caused a test to fail. `Args: test_name: the test's name or unique_id, as returned by list_failing_tests. limit: maximum rows to return (kept small on purpose).`
healthA	Check that the server is configured correctly and can reach its inputs. Verifies the target directory, the required artifacts, and warehouse connectivity.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qraza/dbt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server