MotherDuck
FreeMotherDuck 官方集成，使用 MotherDuck 和本地 DuckDB 查询和分析数据。
FreeFree tier
About MotherDuck
Local MCP server for DuckDB and MotherDuck. Connect AI assistants to your data using DuckDB's powerful analytical SQL engine. Supports connecting to local DuckDB files, in-memory databases, S3-hosted databases, and MotherDuck. Allows executing SQL read- and write-queries, browsing database catalogs, and switching between different database connections on-the-fly.
Key Features
Supports local DuckDB files, in-memory databases, S3-hosted databases, and MotherDuck
Executes SQL read- and write-queries
Browses database catalogs and metadata
Switches between different database connections on-the-fly
Runs in read-only mode by default for security; optional read-write mode
Easy one-click install via uvx for Claude Desktop
Open source and self-hostable
Pros & Cons
Pros
- Open source and free to self-host
- Supports multiple storage backends (local, in-memory, S3, MotherDuck)
- Read-write access when configured
- Easy setup with uvx and Claude Desktop integration
- Flexible database switching at runtime
- Zero-setup remote option available from MotherDuck
Cons
- Requires local installation for self-hosted use
- Read-only by default; write access requires explicit flag and token setup
- MotherDuck connections need a read-scaling token in read-only mode
- Production deployment requires careful security considerations
- S3 integration requires environment variable configuration for authentication
Best For
Connect AI assistants to perform SQL analytics on local and remote dataEnable IDEs to query databases directly for data engineering tasksIntegrate DuckDB's analytical engine into chat-based data analysis workflowsBrowse and explore database catalogs from AI toolsMigrate data between local files, S3, and MotherDuck
FAQ
What is the difference between Remote MCP and Local MCP?
Remote MCP is hosted by MotherDuck with zero setup. Local MCP (this repo) runs locally/self-hosted and requires local installation.
How do I enable write access?
Add the parameter --read-write to enable write access. The server runs in read-only mode by default.
How do I connect to MotherDuck?
Use --db-path md: and provide a MotherDuck token via the motherduck_token environment variable.
Does this support S3-hosted databases?
Yes. You can connect to remote DuckDB files on S3 using s3://bucket/path.duckdb and set up S3 authentication via environment variables.
I'm migrating from v0.x. What changed?
The server now runs in read-only mode by default. The default --db-path changed from md: to :memory:. MotherDuck connections in read-only mode require a read-scaling token.