DuckDB / MotherDuck is a Databases MCP server that lets Claude Code, Cursor, Windsurf and any MCP-compatible AI agent query and analyze data with MotherDuck and local DuckDB. Install in 1 minute with mcpizy install duckdb.
Databases
Query and analyze data with MotherDuck and local DuckDB. In-process analytical database.
mcpizy install duckdbnpx -y @motherduckdb/mcp-serverIf DuckDB / MotherDuck doesn't fit your stack, these Databases MCP servers solve similar problems.
The DuckDB / MotherDuck MCP server is an Databases Model Context Protocol server that lets Claude Code, Cursor, Windsurf, VS Code with Copilot, and other MCP-compatible AI agents query and analyze data with MotherDuck and local DuckDB. It exposes DuckDB / MotherDuck's capabilities as tools the AI can call directly from your editor or CLI.
The fastest way is the MCPizy CLI: run `mcpizy install duckdb` and MCPizy will add the server to your `.claude.json` automatically. You can also install it manually by adding an entry under `mcpServers` in `.claude.json` with the command `npx -y @motherduckdb/mcp-server` and restarting Claude Code.
Yes. The DuckDB / MotherDuck MCP server is free and open source (see the GitHub repository linked on this page). You may still need a DuckDB / MotherDuck account or API key to connect the server to the underlying service, but the MCP layer itself has no MCPizy subscription cost.
Yes. Any MCP-compatible client works — including Claude Code, Claude Desktop, Cursor (via `.cursor/mcp.json`), Windsurf, VS Code with Copilot Chat, and custom agents built on the MCP SDK. The same install command targets all of them; only the config file path differs.
Once installed, your AI agent can query and analyze data with MotherDuck and local DuckDB directly inside your conversation. Typical use cases include asking Claude Code or Cursor to run DuckDB / MotherDuck operations, inspect results, chain DuckDB / MotherDuck with other MCP servers (see our Workflow Recipes), and automate repetitive databases tasks without leaving your editor.