Back to directory

DuckDB / MotherDuck Local MCP Server

An MCP server that connects AI assistants and IDEs to DuckDB's SQL engine, letting them query local DuckDB files, in-memory databases, S3-hosted databases and MotherDuck, browse catalogs, and switch connections at runtime.

DuckDB / MotherDuck Local MCP Server

This server exposes DuckDB and MotherDuck to MCP-compatible clients so they can run read and write SQL queries, browse database catalogs, and switch between different database connections without restarting. It runs locally, in contrast to MotherDuck's separate zero-setup remote MCP server.

It runs in read-only mode by default; a --read-write flag enables writes, and MotherDuck connections in read-only mode need a read-scaling token. The default database is an in-memory DuckDB instance rather than MotherDuck, and a --db-path flag selects a local file, an s3:// path, or md: for MotherDuck.

It installs with uv or uvx, and is configured as an MCP server entry that runs the mcp-server-motherduck command with its arguments.

More in MCP servers

See all 734
  • Light Cloud

    light-cloud.com

    A hosting platform that deploys a static site, a container, or a managed Postgres database straight from a GitHub, GitLab, or Bitbucket push, with a preview URL for every branch and an MCP server for deploying from Claude Code.

  • ForensicDbg

    forensicdbg.com

    A post-mortem debugger for native Windows x86 and x64 crashes, with an MCP interface so AI tools can consume crash-dump analysis directly.

  • Karada.ai

    karada.ai

    A CI/CD platform that auto-compiles existing APIs into Go MCP servers, attaches composable middleware, and exposes them through one gateway usable from Cursor, Claude Code, and Windsurf.