Model Context Protocol low risk

dbt Docs

Exposes dbt project metadata (manifest, catalog) via MCP, enabling search, lineage exploration, and node inspection for dbt projects.

Connections & Capabilities

Connects To

GitHubTwitter

Capabilities

read

Quickstart

Config

{
    "mcpServers": {
        "DBT Docs MCP": {
        "command": "uv",
        "args": [
            "run",
            "--with",
            "networkx,mcp[cli],rapidfuzz,dbt-core,python-decouple,sqlglot,tqdm",
            "mcp",
            "run",
            "/Users/mattijs/repos/dbt-docs-mcp/src/mcp_server.py"
        ],
        "env": {
            "MANIFEST_PATH": "/Users/mattijs/repos/dbt-docs-mcp/inputs/manifest.json",
            "SCHEMA_MAPPING_PATH": "/Users/mattijs/repos/dbt-docs-mcp/outputs/schema_mapping.json",
            "MANIFEST_CL_PATH": "/Users/mattijs/repos/dbt-docs-mcp/outputs/manifest_column_lineage.json"
        }
        }
    }
}

Exposed MCP Tools (8)

safe

search_dbt_node_names

Finds dbt nodes by name.

Read-only search operation.

safe

search_dbt_column_names

Locates dbt nodes based on column names.

Read-only search operation.

safe

search_dbt_sql_code

Searches within the compiled SQL code of dbt nodes.

Read-only search operation.

safe

get_dbt_node_attributes

Retrieves detailed attributes for a given dbt node ID.

Read-only retrieval of node attributes.

safe

get_dbt_predecessors

Finds direct upstream dependencies of a dbt node.

Read-only lineage exploration.

safe

get_dbt_successors

Finds direct downstream dependents of a dbt node.

Read-only lineage exploration.

safe

get_column_ancestors

Traces all upstream sources for a specific column in a model.

Read-only column-level lineage tracing.

safe

get_column_descendants

Traces all downstream dependents of a specific column in a model.

Read-only column-level lineage tracing.

Safety Assessment

This server is relatively safe for read-only access to dbt metadata. The primary risk lies in the exposure of sensitive information within the dbt project itself. Ensure the MANIFEST_PATH is secured and dbt project descriptions are sanitized.

Primarily read-only access to dbt metadata.
No direct database access or modification capabilities.
Limited execution capabilities, focused on metadata retrieval.
Relies on pre-generated dbt artifacts (manifest.json, catalog.json).

Exposure of dbt project metadata if MANIFEST_PATH is not properly secured.
Potential for information leakage if sensitive data is included in dbt descriptions or tags.
Dependency on external libraries (networkx, rapidfuzz, dbt-core) which could introduce vulnerabilities.
Lack of built-in authentication mechanisms beyond environment variables.