dbt-core-mcp and mcp-server-duckdb
These are complements that work together: dbt Core processes and transforms data using SQL models, while DuckDB provides the underlying database engine that can execute those transformations, making them natural partners in a data pipeline architecture.
About dbt-core-mcp
NiclasOlofsson/dbt-core-mcp
dbt Core MCP Server: Interact with dbt projects via Model Context Protocol
Executes dbt commands (runs, tests, builds) within the user's actual environment without requiring dbt-core or adapters to be installed server-side, automatically detecting and respecting the Python environment (uv, poetry, venv, conda) and dbt version in use. Integrates with Claude and other MCP-compatible AI assistants via VS Code, providing full project awareness including lineage analysis, compiled SQL inspection, and CTE debugging to enable true pair-programming workflows without context switching.
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