MotherDuck MCP

Local · stdio

DuckDB is an embeddable analytical database, and MotherDuck is a serverless cloud platform built on top of it. MotherDuck's own mcp-server-motherduck gives agents one SQL interface to both: a local DuckDB file or a cloud database via a motherduck_token. Four tools cover query execution, listing databases and tables, and switching connections. Local files need no authentication at all.

Why this server

execute_query runs DuckDB-dialect SQL — against local files or the MotherDuck cloud alike
A local file or :memory: database — works with no token and no signup at all
switch_database_connection swaps databases without restarting the server
list_databases and list_tables show the structure of both local and cloud-attached databases

Usage examples

Prompt: Analyze this local Parquet file — what's the month-over-month sales trend?

Result: The agent called execute_query on the DuckDB file with a monthly aggregation — no token, no data uploaded anywhere else.

Prompt: Switch to the sales_prod database in MotherDuck cloud and list its tables

Result: switch_database_connection moved to md:sales_prod using the motherduck_token, and list_tables returned the full table list of the cloud database.

Local server

This MCP runs locally on the user's machine (stdio), so availability isn't tracked — rely on reviews and the rating instead.

Reviews

No reviews yet.