MotherDuck's DuckDB MCP Server

An MCP server implementation that interacts with DuckDB and MotherDuck databases, providing SQL analytics capabilities to AI Assistants and IDEs.

Features

Hybrid execution: query data from local DuckDB or/and cloud-based MotherDuck databases
Cloud storage integration: access data stored in Amazon S3 or other cloud storage thanks to MotherDuck's integrations
Data sharing: create and share databases
SQL analytics: use DuckDB's SQL dialect to query any size of data directly from your AI Assistant or IDE
Serverless architecture: run analytics without needing to configure instances or clusters

Components

Prompts

The server provides one prompt:

duckdb-motherduck-initial-prompt: A prompt to initialize a connection to DuckDB or MotherDuck and start working with it

Tools

The server offers one tool:

query: Execute a SQL query on the DuckDB or MotherDuck database
- Inputs:
  - query (string, required): The SQL query to execute

All interactions with both DuckDB and MotherDuck are done through writing SQL queries.

Getting Started

General Prerequisites

uv installed, you can install it using pip install uv or brew install uv

If you plan to use the MCP with Claude Desktop or any other MCP comptabile client, the client need to be installed.

Prerequisites for DuckDB

No prerequisites. The MCP server can create an in-memory database on-the-fly
Or connect to an existing local DuckDB database file , or one stored on remote object storage (e.g., AWS S3).

See Connect to local DuckDB.

Prerequisites for MotherDuck

Sign up for a MotherDuck account
Generate an access token via the MotherDuck UI
Store the token securely for use in the configuration

Usage with Cursor

Install Cursor from cursor.com/downloads if you haven't already
Open Cursor:

To set it up globally for the first time, go to Settings->MCP and click on "+ Add new global MCP server".
This will open a mcp.json file to which you add the following configuration:

{
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck",
        "--db-path",
        "md:",
        "--motherduck-token",
        "<YOUR_MOTHERDUCK_TOKEN_HERE>"
      ]
    }
  }
}

Usage with VS Code

Install with UV in VS Code

Install with UV in VS Code Insiders

For the quickest installation, click one of the "Install with UV" buttons at the top of this README.

Manual Installation

Add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "motherduck_token",
        "description": "MotherDuck Token",
        "password": true
      }
    ],
    "servers": {
      "motherduck": {
        "command": "uvx",
        "args": [
          "mcp-server-motherduck",
          "--db-path",
          "md:",
          "--motherduck-token",
          "${input:motherduck_token}"
        ]
      }
    }
  }
}

Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "motherduck_token",
      "description": "MotherDuck Token",
      "password": true
    }
  ],
  "servers": {
    "motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck",
        "--db-path",
        "md:",
        "--motherduck-token",
        "${input:motherduck_token}"
      ]
    }
  }
}

Usage with Claude Desktop

Install Claude Desktop from claude.ai/download if you haven't already
Open the Claude Desktop configuration file:

To quickly access it or create it the first time, open the Claude Desktop app, select Settings, and click on the "Developer" tab, finally click on the "Edit Config" button.
Add the following configuration to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck",
        "--db-path",
        "md:",
        "--motherduck-token",
        "<YOUR_MOTHERDUCK_TOKEN_HERE>"
      ]
    }
  }
}

Important Notes:

Replace YOUR_MOTHERDUCK_TOKEN_HERE with your actual MotherDuck token
Replace YOUR_HOME_FOLDER_PATH with the path to your home directory (needed by DuckDB for file operations). For example, on macOS, it would be /Users/your_username
The HOME environment variable is required for DuckDB to function properly.

Securing your MCP Server when querying MotherDuck

If the MCP server is exposed to third parties and should only have read access to data, we recommend using a read scaling token and running the MCP server in SaaS mode.

Read Scaling Tokens are special access tokens that enable scalable read operations by allowing up to 4 concurrent read replicas, improving performance for multiple end users while restricting write capabilities. Refer to the Read Scaling documentation to learn how to create a read-scaling token.

SaaS Mode in MotherDuck enhances security by restricting it's access to local files, databases, extensions, and configurations, making it ideal for third-party tools that require stricter environment protection. Learn more about it in the SaaS Mode documentation.

Secure Configuration

{
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck",
        "--db-path",
        "md:",
        "--motherduck-token",
        "<YOUR_READ_SCALING_TOKEN_HERE>",
        "--saas-mode"
      ]
    }
  }
}

Connect to local DuckDB

To connect to a local DuckDB, instead of using the MotherDuck token, specify the path to your local DuckDB database file or use :memory: for an in-memory database.

In-memory database:

{
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck",
        "--db-path",
        ":memory:"
      ]
    }
  }
}

Local DuckDB file:

{
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck",
        "--db-path",
        "/path/to/your/local.db"
      ]
    }
  }
}

Example Queries

Once configured, you can e.g. ask Claude to run queries like:

"Create a new database and table in MotherDuck"
"Query data from my local CSV file"
"Join data from my local DuckDB database with a table in MotherDuck"
"Analyze data stored in Amazon S3"

Testing

The server is designed to be run by tools like Claude Desktop and Cursor, but you can start it manually for testing purposes. When testing the server manually, you can specify which database to connect to using the --db-path parameter:

Default MotherDuck database:
- To connect to the default MotherDuck database, you will need to pass the auth token using the --motherduck-token parameter.
```
uvx mcp-server-motherduck --db-path md: --motherduck-token <your_motherduck_token>
```

Specific MotherDuck database:

uvx mcp-server-motherduck --db-path md:your_database_name --motherduck-token <your_motherduck_token>

Local DuckDB database:

uvx mcp-server-motherduck --db-path /path/to/your/local.db

In-memory database:

uvx mcp-server-motherduck --db-path :memory:

If you don't specify a database path but have set the motherduck_token environment variable, the server will automatically connect to the default MotherDuck database (md:).

Running in SSE mode

The server could also be running SSE mode using supergateway by running the following command:

npx -y supergateway --stdio "uvx mcp-server-motherduck --db-path md: --motherduck-token <your_motherduck_token>"

And you can point your clients such as Claude Desktop, Cursor to this endpoint.

Development configuration

To run the server from a local development environment, use the following configuration:

 {
  "mcpServers": {
    "mcp-server-motherduck": {
      "command": "uv",
      "args": [
        "--directory", 
        "/path/to/your/local/mcp-server-motherduck", 
        "run", 
        "mcp-server-motherduck", 
        "--db-path",
        "md:",
        "--motherduck-token",
        "<YOUR_MOTHERDUCK_TOKEN_HERE>"
      ]
    }
  }
}

Troubleshooting

If you encounter connection issues, verify your MotherDuck token is correct
For local file access problems, ensure the --home-dir parameter is set correctly
Check that the uvx command is available in your PATH
If you encounter spawn uvx ENOENT errors, try specifying the full path to uvx (output of which uvx)
In version previous for v0.4.0 we used environment variables, now we use parameters

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.