DuckDB MCP Server
Related Servers
Alternatives to DuckDB MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceQuery local CSV, Parquet, JSON and TSV files with real SQL via DuckDB. Gives your AI coding tool ground-truth data access instead of hallucinated answers.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables executing SQL queries on DuckDB databases locally or on MotherDuck cloud, with support for multiple databases, read-only mode, and Claude Desktop integration.MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with a DuckDB database by executing arbitrary SQL through a single unified query tool, supporting operations such as querying, table creation, and schema inspection. Supports a read-only mode that enforces DuckDB's native protection to prevent any writes.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with a local DuckDB database through a single unified SQL query tool, supporting operations such as querying, table creation, joins, and schema inspection. Optional read-only mode enforces native write protection so data can be analyzed safely without unintended changes.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query business databases directly via natural language, with enforced read-only access and secure query limits. Supports SQLite and PostgreSQL, and works with any OpenAI-compatible model.0ISC
- AlicenseAqualityDmaintenanceEnables AI assistants to connect to and interact with PostgreSQL, MySQL, SQLite, and MongoDB databases through natural language, supporting schema exploration, query execution, data export, and more.13MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'query' has a clear and distinct purpose for executing queries on the DuckDB database.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'query' follows a simple, clear pattern with no deviations or mixed conventions to evaluate.
A single tool for a database server is too few for the apparent scope, as it lacks basic operations like creating tables, inserting data, or managing connections. This minimal set will likely cause agent failures in handling typical database workflows.
The tool surface is severely incomplete for a database server. It only provides query execution, missing essential CRUD operations (e.g., create, read, update, delete), schema management, and other database functionalities, leading to significant gaps in coverage.