topmcps
Browse MCPs
DuckDB

DuckDB

In-process analytical SQL over files and Parquet from an AI agent.

Score 82(?)MotherDuckMIT484Verified Top MCPs for Databases →
InstallView on GitHub

Quick answer

What it does

Spawns an in-process DuckDB instance and exposes SQL execution against local files, Parquet, CSV, JSON, and (optionally) S3/GCS object storage.

Best for

  • Local CSV / Parquet analysis
  • Ad-hoc data exploration
  • S3 dataset queries
  • Quick joins across files

Not for

  • Multi-user concurrent writes
  • Transactional OLTP

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "duckdb": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck"
      ],
      "env": {
        "motherduck_token": "${motherduck_token}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export motherduck_token=optional-for-cloud-mode
claude mcp add duckdb -- uvx mcp-server-motherduck

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "duckdb": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck"
      ],
      "env": {
        "motherduck_token": "${motherduck_token}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "duckdb": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck"
      ],
      "env": {
        "motherduck_token": "${motherduck_token}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "duckdb": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck"
      ],
      "env": {
        "motherduck_token": "${motherduck_token}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "duckdb": {
      "command": "uvx",
      "args": [
        "mcp-server-motherduck"
      ],
      "env": {
        "motherduck_token": "${motherduck_token}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "uvx",
          "args": [
            "mcp-server-motherduck"
          ],
          "env": {
            "motherduck_token": "${motherduck_token}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.duckdb]
command = "uvx"
args = [
  "mcp-server-motherduck",
]
env = { motherduck_token = "${motherduck_token}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "duckdb": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-server-motherduck"
        ]
      },
      "env": {
        "motherduck_token": "${motherduck_token}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    DuckDB doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set motherduck_token in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

ToolDescriptionArgsSide effects
queryRun a DuckDB SQL statement.sql: stringRead
attach_fileRead a CSV / Parquet / JSON file as a queryable view.path: string, name?: stringRead

Security & scope

Access scope
Read + write
Sandbox
Spawns a local DuckDB process. Filesystem reads scoped to the working directory unless you pass absolute paths. Remote reads use whatever AWS / GCS credentials are in the environment — the MCP forwards them, it does not store them.
Gotchas
  • COPY TO can write files anywhere the process can reach. Run the MCP under a dedicated user if you care about scoping writes.
  • httpfs follows redirects — be aware when querying URLs the model has discovered.
  • MotherDuck mode sends queries to a remote service; the token is in env, so treat it like any other API key.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. databases work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-databases
Compare DuckDB against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare DuckDB MCP vs [Postgres MCP Pro MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/duckdb
- top-mcps.com listing for Postgres MCP Pro
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the DuckDB MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/duckdb (fetch https://top-mcps.com/mcp/duckdb.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (motherduck_token) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Databases MCPs

Other tools in the same category worth evaluating.

Postgres MCP ProPRO

Production-grade Postgres MCP with index advice, EXPLAIN, and health checks.

database, sql, postgres, performance
5 minMedium
SQLite

Local SQLite database access with full read/write support.

database, sqlite, local, storage
2 minLow
Supabase logo — MCP server

Full Supabase access: database, auth, storage, and edge functions.

supabase, database, backend, postgres
5 minLow

Compared with DuckDB

Side-by-side breakdowns for the choices people most often weigh against this MCP.

DuckDBvsPostgres MCP ProDuckDBvsSQLiteDuckDBvsBigQueryDuckDBvsMongoDB

Exploring Top MCPs for Databases? See all Databases MCPs →