← ClaudeAtlas

duckdb-quacklisted

Serve DuckDB 2.0 over HTTP with the Quack protocol, or route a session to Quack, PostgreSQL, or MySQL with CONNECT. Covers tokens, TLS reverse proxies, pushdown, and connection management. Use when the user says quack, duckdb -serve, duckdb -connect, CONNECT, or remote pushdown.
srimon12/duckdb-2-skills · ★ 1 · API & Backend · score 65
Install: claude install-skill srimon12/duckdb-2-skills
# Quack and CONNECT Quack turns a DuckDB process into an HTTP server, defaulting to `quack:localhost` on port `9494` over plain HTTP. DuckDB automatically installs and loads the extension on first use. Result payloads use native DuckDB binary serialization, keeping decimals, intervals, and nested structures strongly typed. The protocol is in beta and suited for prototyping, not production. Upgrades may introduce breaking changes across the wire protocol, function names, and default settings. An active server exposes the entire SQL surface, including writes, under the host OS identity of the user who started it. Because a server process is long-running, start it in the background and do not block the active session. For CLI execution guidelines, consult `duckdb`. ## Serve To serve a database over HTTP from the CLI, run: ```bash duckdb analytics.duckdb -serve ``` When omitting the database path, `-serve` serves an in-memory database. Serving a Parquet or CSV file exposes a view named after the file stem: `duckdb runs.parquet -serve` exposes `runs`. When no default Quack secret exists, `-serve` generates a token and persists an unencrypted secret named `__default_quack` (scope `quack:`, mode 600) so `duckdb -connect` works immediately. Because possession of the token grants full read and write access to every session table, delete `__default_quack` when stopping the server, or load a named secret from a vault. In a non-interactive shell, `-serve` exits after printing the