DuckDB is an in-process SQL OLAP database management system designed for analytical queries with a simple, embeddable architecture that supports various programming languages and platforms.
Why this server?
Allows running data quality validation rules against a DuckDB database, including completeness, uniqueness, and statistical checks.
Why this server?
Connects to DuckDB databases to run SQL queries and generate insights from the data
Why this server?
Connects to DuckDB databases for profiling and monitoring.
Why this server?
Manages multi-tenant DuckDB databases with query execution, caching, and built-in UI.
Why this server?
Enables querying of geographic data stored in parquet files via DuckDB's HTTP filesystem support.
Why this server?
The server implementation was inspired by and incorporates code from mcp-server-duckdb, suggesting potential DuckDB database connectivity capabilities.
Why this server?
Uses DuckDB to query provider-level Medicaid claims data from local Parquet files, enabling high-performance analysis of HCPCS codes, NPI-specific spending, and service summaries.
Why this server?
Uses DuckDB as a local cache for high-performance SQL queries, statistical analysis, and geospatial operations on downloaded open data.
Why this server?
Supports working with DuckDB as a database backend for dbt projects, as shown in the profiles.yml example.
