mcp-server-duckdb
Related Servers
Alternatives to mcp-server-duckdb
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables interaction with DuckDB databases through MCP, allowing SQL querying, table creation, and schema inspection with optional read-only protection.-
- FlicenseNot gradedqualityAmaintenanceEnables interaction with a DuckDB database through MCP tools for executing SQL queries, creating tables, and inspecting schemas. It also supports read-only mode to prevent write operations.-
- FlicenseNot gradedqualityAmaintenanceEnables interaction with a DuckDB database through MCP tools, allowing SQL query execution, table creation, schema inspection, and optional read-only access to protect data integrity.-
- FlicenseNot gradedqualityAmaintenanceEnables interacting with a DuckDB database through MCP tools for SQL querying, table creation, and schema inspection, with optional read-only enforcement.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to interact with a DuckDB database by executing SQL queries, creating tables, and inspecting schemas through a unified query tool. Supports optional read-only mode to prevent write operations and maintain data integrity.-
- FlicenseNot gradedqualityAmaintenanceEnables executing SQL queries and inspecting or modifying DuckDB database schemas through MCP, with optional read-only mode and connection reuse for secure local analysis.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The 'query' tool has a single, unambiguous purpose of executing DuckDB queries.
The single tool name 'query' is a clear, straightforward verb that accurately describes its function. With only one tool, naming consistency is trivially satisfied.
One tool is on the thin side for a full database server like DuckDB. While a generic query tool can cover many operations, it lacks typical helper tools (e.g., schema listing, table inspection) that agents might expect, making the count borderline.
The query tool can execute any SQL, enabling full CRUD and DDL operations, so there are no direct dead ends. However, there is no built-in schema discovery or validation, which is a minor gap that agents can work around via SQL queries against system tables.