exclude

MCP tool from Dbt Core MCP by NiclasOlofsson

Exclude models

How to use it

exclude is exposed by the Dbt Core MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the exclude tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

FULL DBT CORE MCP LISTING

Other tools in Dbt Core MCP (32)

analyze_impact

Analyze the blast radius of changing any resource - shows all downstream dependencies that would be affected.

build_models

Run models and tests together in dependency order (most efficient approach). Supports state-based selection.

check_schema_changes

Detect column additions/removals

column_name

Name of the column to trace

dependencies

Source columns and tables with full qualification

depth

Maximum levels to traverse (None for unlimited, 1 for immediate, etc.)

direction

"upstream" (sources), "downstream" (dependents), or "both" (default)

fail_fast

Stop on first failure

full_refresh

Force full refresh for incremental models

get_column_lineage

Trace column-level lineage through SQL transformations - see exactly how columns flow through CTEs, joins, aggregations, and transformations.

get_lineage

Trace dependency relationships for any resource - shows what it depends on (upstream) and what depends on it (downstream).

get_project_info

Get basic information about your dbt project including name, version, adapter type, and resource counts. By default, also runs dbt debug to validate your environment and test the database connection.

get_resource_info

Get detailed information about any resource - works for models, sources, seeds, snapshots, and tests.

include_compiled_sql

Include compiled SQL with Jinja resolved (default: true, models only)

include_database_schema

Include actual column types from database (default: true)

install_deps

Install dbt packages defined in packages.yml to enable interactive package management workflow.

list_resources

List all resources in your project, or filter by type (models, sources, seeds, snapshots, tests).

model_name

Name of the dbt model to analyze

name

Resource name (e.g., "customers", "jaffleshop.raworders")

query_database

Execute SQL queries against your database using dbt's ref() and source() functions. Results can be displayed inline or exported to CSV/TSV files for analysis.

resource_type

Optional filter - "model", "source", "seed", "snapshot", "test", or None for all

run_debug

Run dbt debug to validate environment and test connection (default: True)

run_models

Run dbt models with state-based selection for fast development. Requires previous state (from a prior run) to detect modifications.

seed_data

Load seed data (CSV files) from seeds/ directory into database tables.

select

Model selector (e.g., "customers", "tag:mart")

select_state_modified

Run only models that changed (requires previous state)

select_state_modified_plus_downstream

Run changed models + everything downstream

show

Show preview of loaded data

snapshot_models

Execute dbt snapshots to capture slowly changing dimensions (SCD Type 2).

test_models

Run dbt tests with state-based selection. Requires previous state to detect modifications.

transformations

Detailed transformation at each step (CTE name, column, SQL expression)

via_ctes

List of CTE names in transformation order (shows the path through internal CTEs)