In-depth architectural comparison of the Dbt Docs MCP and MCP Databricks Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Dbt Docs MCP
Data Platforms · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
MCP Databricks Server
Data Platforms · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Dbt Docs MCP if you need specialized Data Platforms tools running via a local process. Choose MCP Databricks Server if your workspace requires Data Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Dbt Docs MCP when:
You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: MANIFEST_PATH, SCHEMA_MAPPING_PATH, MANIFEST_CL_PATH.
Primary tools included: Search nodes by name, column, or SQL code, Get node attributes by unique ID, Find direct upstream and downstream nodes.
MCP server for dbt-core (OSS) users as the official dbt MCP only supports dbt Cloud. Supports project metadata, model and column-level lineage and dbt documentation.
Connect to Databricks API, allowing LLMs to run SQL queries, list jobs, and get job status.
Dbt Docs MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, MCP Databricks Server belongs to Data Platforms using local stdio subprocess. Select Dbt Docs MCP when you need capabilities focused on data platforms and MCP Databricks Server when you require tools for data platforms.