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?
Enables querying the code search index and knowledge graph as SQL tables via HTTP API, allowing correlation with other data sources in DuckDB.
Why this server?
Integrates with local DuckDB to provide SQL analytics capabilities and allow querying data from local databases
Why this server?
Provides spatial SQL execution using DuckDB's dialect, including ST_* functions and file reading via read_parquet/ST_Read, enabling SQL-based geoprocessing and materialization of results as GeoParquet with provenance.
Why this server?
Provides DuckDB as the built-in local warehouse for Semantic Rails, supporting semantic queries, validation, and execution without additional connectors.
Why this server?
Allows running data quality validation rules against a DuckDB database, including completeness, uniqueness, and statistical checks.
Why this server?
Uses DuckDB as the backend database for fast and efficient querying of health data, enabling complex SQL queries on exported Apple Health information.
Why this server?
Allows querying financial evidence from money markets, bank risk, market liquidity, and China economy data through DuckDB using HTTP-backed views.
Why this server?
Supports working with DuckDB as a database backend for dbt projects, as shown in the profiles.yml example.
Why this server?
Connects to DuckDB databases to run SQL queries and generate insights from the data
