A DuckDB MCP server
A DuckDB MCP server. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.
A Model Context Protocol (MCP) server implementation for DuckDB, providing database interaction capabilities through MCP tools. It would be interesting to have LLM analyze it. DuckDB is suitable for local analysis.
This server enables interaction with a DuckDB database through the Model Context Protocol, allowing for database operations like querying, table creation, and schema inspection.
Everything the assistant can do here goes through one of these:
query — Execute any SQL query on the DuckDB databaseInput — query (string) - Any valid DuckDB SQL statementOutput — Query results as text (or success message for operations like CREATE/INSERT)Resources — The Resources tool exposed by this serverPrompts — The Prompts tool exposed by this serverTools — The server implements the following database interaction tool:MacOS — Location: ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows — The Windows tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverDebugging — Debugging MCP servers can be challenging due to their stdio-based communication. We recommend using the [MCP@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
uv package manager - DuckDB Python package - MCP server dependenciesThis sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — query, Input, Output and 7 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| query | Execute any SQL query on the DuckDB database |
| Input | query (string) - Any valid DuckDB SQL statement |
| Output | Query results as text (or success message for operations like CREATE/INSERT) |
| Resources | The Resources tool exposed by this server. |
| Prompts | The Prompts tool exposed by this server. |
| Tools | The server implements the following database interaction tool: |
| MacOS | Location: ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | The Windows tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Debugging | Debugging MCP servers can be challenging due to their stdio-based communication. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) for the best debugging experience. |
{
"mcpServers": {
"server-duckdb": {
"command": "npx",
"args": ["-y", "@smithery/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
uv package manager - DuckDB Python package - MCP server dependenciesRead-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.