Skip to content
AI Dev Toolkit.
Esc
  • AI Token CounterCount tokens for GPT, Claude, Gemini, DeepSeek, Qwen and more.Tool
  • LLM API Cost CalculatorEstimate per-request, daily and monthly API costs.Tool
  • AI Model ComparisonCompare prices, context windows and features across models.Tool
  • AI Model Pricing PagesSpecs, real costs and cheaper alternatives for popular models.Tool
  • Context Window CheckerSee whether your text fits each model’s context window.Tool
  • Subscription vs API CalculatorFind out whether a chat plan or the API is cheaper for you.Tool
  • GPU / VRAM CalculatorCheck how much VRAM a local model needs and which GPUs fit.Tool
  • Prompt Caching CalculatorEstimate savings from prompt caching.Tool

MCP server · Databases

DuckDB / MotherDuck Local MCP server

Lets an assistant run DuckDB SQL on local files, in-memory databases, S3-hosted databases or MotherDuck, read-only unless you allow writes.

Maintainer
MotherDuck (official)
Licence
MIT
Runs
Locally (uvx)
Sign-in
Optional token
Registry version
1.1.0 (updated 2026-10-07)
Last activity
2026-10-07

Overview

What it does

This server from MotherDuck runs DuckDB through uvx. You give it a database path: a local .duckdb file, :memory:, an s3:// URL or md: for MotherDuck, which also needs a MotherDuck token. It then exposes a small set of tools to run SQL and browse databases, tables and columns. Results are capped at 1,024 rows and 50,000 characters by default.

Connections are read-only unless you add --read-write. A read-only connection to a local file does not hold the file lock, so you can keep writing to it from another tool. The --allow-switch-databases flag lets the assistant move between databases while it runs. It is a good choice for quick analysis of local data files and DuckDB databases. MotherDuck also runs a hosted remote MCP server, which it recommends when third parties need access.

Tools

What the assistant can do

  • execute_query in the DuckDB SQL dialect
  • list_databases, list_tables and list_columns
  • switch_database_connection (with --allow-switch-databases)
  • Local files, in-memory, S3 and MotherDuck databases
  • Row, character and timeout limits on results

Install

Install DuckDB / MotherDuck Local MCP server in your app

You need:

  • uv (provides uvx)
  • A MotherDuck account and token only if you connect to MotherDuck

Run in your project. --scope local keeps the servers private to you in this project; use user for every project.

Terminal
claude mcp add --scope local motherduck -- uvx mcp-server-motherduck --db-path /absolute/path/to/your.duckdb
Native Windows (PowerShell)
claude mcp add --scope local motherduck -- uvx mcp-server-motherduck --db-path /absolute/path/to/your.duckdb

Want it alongside other servers? Open DuckDB / MotherDuck Local MCP Server in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.

Before you install

  • Read-only by default; --read-write lets the assistant change data.
  • MotherDuck notes that read-only mode alone still allows local filesystem access and changes to DuckDB settings; use --init-sql or SaaS mode to lock it down before sharing access.
  • Pass the MotherDuck token through the motherduck_token environment variable rather than on the command line.
  • A local MCP server runs with your user account’s permissions. Install it only from the source linked above. See how to choose a safe server.

Why it’s listed

Why we list it

Vendor-maintained, simple to start and handy for local analytics on files and DuckDB databases.

Related

All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?