mcp server duckdb
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.
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.
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.
Currently, no custom resources are implemented.
Currently, no custom prompts are implemented.
The server implements the following database interaction tool:
query
(string) - Any valid DuckDB SQL statement[!NOTE] The server provides a single unified
query
function rather than separate specialized functions, as modern LLMs can generate appropriate SQL for any database operation (SELECT, CREATE TABLE, JOIN, etc.) without requiring separate endpoints.[!NOTE] When the server is running in
readonly
mode, DuckDB's native readonly protection is enforced. This ensures that the Language Model (LLM) cannot perform any write operations (CREATE, INSERT, UPDATE, DELETE), maintaining data integrity and preventing unintended changes.
--readonly
is specified and the database file does not exist, the server will fail to start with an errorread_only=true
, preventing any write operations.To install DuckDB Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install mcp-server-duckdb --client claude
Configure the MCP server in Claude Desktop's configuration file:
Location: ~/Library/Application Support/Claude/claude_desktop_config.json
Location: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"duckdb": {
"command": "uvx",
"args": [
"mcp-server-duckdb",
"--db-path",
"~/mcp-server-duckdb/data/data.db"
]
}
}
}
~/mcp-server-duckdb/data/data.db
should be replaced with the actual path to the DuckDB database file.uv
package managerDebugging MCP servers can be challenging due to their stdio-based communication. We recommend using the MCP Inspector for the best debugging experience.
Install the inspector using npm:
npx @modelcontextprotocol/inspector uv --directory ~/codes/mcp-server-duckdb run mcp-server-duckdb --db-path ~/mcp-server-duckdb/data/data.db
Open the provided URL in your browser to access the debugging interface
The inspector provides visibility into: - Request/response communication - Tool execution - Server state - Error messages
[
{
"description": "Execute a SELECT query on the DuckDB database",
"inputSchema": {
"properties": {
"query": {
"description": "SELECT SQL query to execute",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "read-query"
},
{
"description": "List all tables in the DuckDB database",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "list-tables"
},
{
"description": "Get the schema information for a specific table",
"inputSchema": {
"properties": {
"table_name": {
"description": "Name of the table to describe",
"type": "string"
}
},
"required": [
"table_name"
],
"type": "object"
},
"name": "describe-table"
},
{
"description": "Execute an INSERT, UPDATE, or DELETE query on the DuckDB database",
"inputSchema": {
"properties": {
"query": {
"description": "SQL query to execute",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "write-query"
},
{
"description": "Create a new table in the DuckDB database",
"inputSchema": {
"properties": {
"query": {
"description": "CREATE TABLE SQL statement",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "create-table"
}
]