DuckDB is an in-process SQL OLAP database management system. Simple, feature-rich, fast & open source.
Used by data teams in Big Tech, finance and startups Use DuckDB's friendly but powerful SQL dialect to query any data source (Parquet, JSON, S3, data lakes, etc.) We made sure that you can install DuckDB in just a few seconds, and built it on familiar technologies so you can start using it immediately. We support a wide range of industry standard technologies (e.g., Parquet, SQL, S3 API) and combine them into a seamless user experience. We built DuckDB on a fast columnar storage engine. DuckDB can spill to disk to support workloads far larger than the available system memory. We release DuckDB, its core extensions and the DuckLake format under MIT, a permissive open-source license. We distribute DuckDB for all popular operating systems and ship idiomatic client APIs for major programming languages. We created a powerful extension mechanism that enables adding new features. In fact, we implemented many core DuckDB features as extensions. DuckDB has native clients and integrations with the data ecosystem Start using DuckDB in your environment
Mentions (30d)
0
Reviews
0
Platforms
2
Sentiment
0%
0 positive
Features
Industry
information technology & services
Employees
26
20
npm packages
40
HuggingFace models
I built a text-to-SQL MCP for all your databases
Been tinkering with MCP servers for a while and got tired of how much boilerplate it takes to give Claude access to my databases and explain them. So I built Statespace: the whole idea is that you declare your MCP's instructions AND tools in Markdown/YAML. Here's a minimal example for Postgres: README.md --- tools: - [psql, -d, $DB, -c, { regex: "^SELECT\\b.*" }] --- # Instructions - Learn the schema by exploring tables, columns, and relationships - Translate the user's question into a query that answers it That regex field is the permission boundary. Claude can only run queries that start with SELECT. No drops, no updates. That's it. That's your entire MCP app. MCP config: "statespace": { "command": "npx", "args": ["statespace", "mcp", "path/to/README.md"], "env": { "DB": "postgresql://user:pass@host:port/db" } } Then just ask: claude "How many users signed up last week? ... As the app grows you can add more files (e.g., schema docs, Python scripts, whatever) and list more tools in the YAML frontmatter. Multi-page apps are also supported Supports PostgreSQL, MySQL, SQLite, Snowflake, MongoDB, DuckDB, MSSQL, and just about any database with a CLI. Happy to answer questions! GitHub Repo: https://github.com/statespace-tech/ssp A ⭐ on GitHub really helps with visibility! submitted by /u/Durovilla [link] [comments]
View originalDuckdb-skill: DuckDB-powered skills for data exploration and session memory
The skills supported include: + read-file and query - uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db - gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs - uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions. Link: https://github.com/duckdb/duckdb-skills Besides the above, duckdb is a really helpful tool if you do any kind of data analysis, Claude usually doesnt default to it but it performs a lot better than pandas, which is usually the default. Does anyone else use it with Claude? submitted by /u/quaintquine [link] [comments]
View originalRepository Audit Available
Deep analysis of duckdb/duckdb — architecture, costs, security, dependencies & more
DuckDB uses a tiered pricing model. Visit their website for current pricing details.
Key features include: Simple, Feature-rich, Portable, Extensible, DuckDB Now Speaks Dutch!.
