| FMRS | 60 / 100 · C | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 12 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 15 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 15 / 20 |
|---|
| Best for | - Data scientists and analysts needing SQL analytics on local or remote databases
- Developers wanting AI-assisted data engineering within IDEs
- Teams needing to quickly explore DuckDB files
- Users who want to incorporate MotherDuck cloud capabilities
| - Teams already using ClickHouse who want AI assistants to access data directly.
- Scenarios requiring fast, read-only data queries and schema exploration.
| - Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
- Scenarios needing a unified MCP setup across multiple database engines
|
|---|
| Not for | - Users who want a fully managed remote MCP service without local installation
- Production environments with strict security requirements (default read-only mode still allows local filesystem access)
- Third-party access without additional security configurations
| - Scenarios requiring write access to the database without explicit opt-in.
- Production environments with stringent security requirements that avoid default permission settings.
| - Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
|
|---|
| Required permissions | - Access to local filesystem (to read DuckDB files or export data)
- Reads environment variables for MotherDuck tokens and AWS credentials
- Executes SQL queries in read-only mode by default; write access must be explicitly enabled
- Optionally switches database connections at runtime (requires --allow-switch-databases)
| - Requires read-only access to ClickHouse database (default).
- Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
- Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
| - Database credentials (username/password/connection string) are supplied via env vars or config
- A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
|
|---|
| Risks and side effects | - If write mode is enabled, data in databases could be modified or deleted
- By default, when exposed to third parties, local filesystem or sensitive data may be accessed
- MotherDuck tokens or AWS credentials could be leaked if misconfigured
- Queries may consume significant resources (memory, CPU) or time out
| - If write access is enabled, AI might make unintended modifications.
- If DROP access is enabled, data deletion could occur accidentally.
- Credentials may be exposed via environment variables.
| - If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
- The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
|
|---|
| Supported clients | Claude Desktop, Claude Code, Codex CLI, Gemini CLI, Cursor, VS Code, Kiro | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 5 | 4 | 0 |
|---|