MCP.so
ログイン

MCP Server Duckdb

@ktanaka101

基本情報

カテゴリ

データベース

ライセンス

MIT

トランスポート

stdio

作者

ktanaka101

MCP Server Duckdb について

A Model Context Protocol (MCP) server implementation for DuckDB, providing database interaction capabilities

MCP Server Duckdb の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-server-duckdb": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "mcp-server-duckdb",
        "--client",
        "claude"
      ]
    }
  }
}

MCP Server Duckdb のツール

1

Execute any SQL query on the DuckDB database

概要

What is mcp-server-duckdb?

A Model Context Protocol (MCP) server that enables interaction with a DuckDB database through MCP tools, allowing LLMs to execute SQL queries, manage tables, and inspect schemas. It is designed for local data analysis.

How to use mcp-server-duckdb?

Install via Smithery or configure in Claude Desktop’s JSON file using uvx mcp-server-duckdb --db-path <path>. Optionally add --readonly or --keep-connection flags. The server accepts a single required parameter db-path and two optional flags.

Key features of mcp-server-duckdb

  • Execute any SQL query via a single unified query tool.
  • Optional read‑only mode using DuckDB’s native protection.
  • Optional persistent connection for TEMP objects and faster queries.
  • Auto‑creates database file and parent directories (unless readonly).
  • Integrates with MCP for LLM‑driven database interaction.

Use cases of mcp-server-duckdb

  • LLM‑powered exploratory analysis on local DuckDB files.
  • Automated table creation, schema inspection, and data insertion.
  • Read‑only query access for security‑sensitive environments.
  • Seamless integration with AI assistants for database operations.

よくある質問

1

How does read‑only mode differ from read‑write?

In read‑only mode the DuckDB database is opened with `read_only=True`, preventing any write operations (CREATE, INSERT, UPDATE, DELETE) and refusing to create missing database files. Read‑write mode allows full SQL and auto‑creates missing files.

2

What are the runtime requirements?

Python with the `uv` package manager, the DuckDB Python package, and MCP server dependencies.

3

Where is the database file stored?

The path is specified by the user via the `--db-path` argument. The server creates the file and any needed parent directories unless `--readonly` is used and the file does not exist.

4

Does the server offer separate tools for different operations?

No, it provides a single unified `query` tool. The LLM generates appropriate SQL for any operation (SELECT, CREATE, INSERT, etc.) without requiring separate endpoints.

5

What transport does the server use?

It uses stdio-based communication, typical of MCP servers. Debugging is recommended with the MCP Inspector, which can be launched via `npx @modelcontextprotocol/inspector`.

コメント

「データベース」の他のコンテンツ