QueryPilot MCP
Related Servers
Alternatives to QueryPilot MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to explore and analyse local CSV, Parquet or JSON files through validated read-only SELECT queries, with schema discovery, profiling and query-plan tools. Results are capped, timed, PII-masked and audit-logged inside a locked DuckDB sandbox that cannot write, reach the network or read other files.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Desktop, Claude Code and Cursor to safely explore local CSV, Excel, Parquet and SQLite files by running guarded read-only DuckDB SQL over a sandboxed data directory. It also supports data profiling, chart generation as image content, and exporting query results, without ever allowing writes or access outside the configured folder.MIT
- AlicenseNot gradedqualityBmaintenanceQuery 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.5MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to list, describe, profile, sample, and run read-only SQL over local CSV, Parquet, and JSON files confined to user-approved folders. Queries are sandboxed with row caps, timeouts, and blocked write/DDL statements for safe by-default access.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to run read-only SQL over local CSV, Parquet, and JSON files through MCP tools, with directory sandboxing, statement gating, timeouts, and query timeouts that keep access confined to permitted folders. Results are shaped for small context windows with row caps, truncation notices, and markdown/CSV/JSON output.MIT
- 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.-
TDQS
Scored across 5 tools
Each tool targets a distinct stage of the data exploration workflow: discovering tables, inspecting schema/stats, sampling rows, retrieving glossary definitions, and executing SQL. The only mild overlap is between describe_table and get_definitions, but one gives schema/statistics while the other gives business semantics, so an agent can easily choose correctly.
All tool names follow a clear verb_noun pattern (list_tables, describe_table, sample_rows, get_definitions, run_query). The wording is predictable and readable, with no mixed casing or inconsistent verb styles.
Five tools is well-scoped for a read-only DuckDB query assistant. Every tool adds a necessary capability, and there is no redundant or filler tool.
The surface covers the core read-only lifecycle: discover tables, inspect schemas, sample data, understand business terms, and run constrained SELECT queries. Minor gaps exist around searching for columns by name, inspecting relationships/foreign keys, or explaining query plans, but agents can work around these using describe_table and run_query.