dbt-mcp and mcp-server-duckdb
These are complements that work together: dbt transforms and models data logic while DuckDB provides the underlying database engine for executing those transformations and queries, making them natural partners in a data workflow rather than alternatives.
About dbt-mcp
dbt-labs/dbt-mcp
A MCP (Model Context Protocol) server for interacting with dbt.
Exposes dbt project metadata and operations through 40+ tools across Discovery API, Semantic Layer, SQL execution, and dbt CLI capabilities—enabling AI agents to query lineage, model details, metrics, and trigger jobs. Connects to dbt Core, Fusion, and Platform environments, supporting both local manifest inspection and cloud-based operations with optional column-level lineage analysis via the Fusion engine.
About mcp-server-duckdb
ktanaka101/mcp-server-duckdb
A Model Context Protocol (MCP) server implementation for DuckDB, providing database interaction capabilities
Exposes DuckDB through a unified `query` tool that accepts arbitrary SQL, enabling LLMs to perform analysis, schema inspection, and data operations on local databases. Supports read-only mode with DuckDB's native write protection and optional connection pooling for persistent state. Integrates with Claude Desktop and other MCP clients via stdio transport, with debugging support through the MCP Inspector.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work