| FMRS | 73 / 100 · B | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 16 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 18 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 15 / 20 |
|---|
| Best for | - Developers and non-developers who want to manage Neon databases via natural language.
- Users who want to perform database tasks quickly within IDEs or chat interfaces.
- Teams needing safe migrations and query optimization.
| - 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 | - Production environments requiring fine-grained control.
- Users needing a full SQL interface and complex transaction handling.
- Users who want to run fully offline or without depending on remote services.
| - 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 | - Neon account and authentication (OAuth or API key).
- Access, create, modify, and delete Neon projects, branches, databases, and resources.
- Execute SQL queries (read/write).
- Manage authentication and Data API configurations.
- Read logs and documentation index.
| - 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 | - Natural language requests may accidentally execute destructive operations (e.g., deleting projects or branches).
- Unauthorized individuals may access your account via API key or OAuth.
- Production use carries risk of accidental changes; official recommendation is for local development only.
- Careful review of LLM-proposed actions is required.
| - 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, Cursor, VS Code, Claude Code, Kiro | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 34 | 4 | 0 |
|---|