Connect to MotherDuck

Use this skill when establishing database connectivity from any application, script, or service to MotherDuck. Start here before running queries or loading data.

Source Of Truth

• Prefer current MotherDuck connection, attach-mode, read-scaling, and multithreading docs.
• If the MotherDuck MCP ask_docs_question feature is available, use it first for current connection behavior.
• When it is unavailable, verify guidance against the public docs before making firm claims about connection strings, token types, or read-scaling behavior.

Default Posture

• Start with the PG endpoint for backend applications that want PostgreSQL wire compatibility.
• Use the native DuckDB API only when you need local files, hybrid local/cloud execution, or direct DuckDB control.
• Use md: workspace connections for multi-database exploration, bootstrap flows, and temporary validation environments.
• Start with one connection. Add pooling or read scaling only when real concurrent-read pressure exists.
• Treat custom_user_agent watermarking as a native DuckDB pattern, not a PG endpoint pattern.

Workflow