| FMRS | 59 / 100 · C | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 15 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 | 15 / 20 |
|---|
| Best for | - Developers using AI coding assistants (like Cursor, Claude Code) who want full-stack development on Tencent Cloud
- Teams that need rapid setup of apps with login, database, and permissions
- Developers who want to perform environment configuration, database operations, and deployment from chat
| - 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 only need static hosting or frontend deployment without backend services
- Users who cannot review AI-proposed sensitive actions (as the AI can directly modify data and permissions)
- Users who do not want to use Tencent Cloud 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 | - Requires login and access to a CloudBase environment
- Access to database, cloud functions, storage, and other resources
- May need elevated permissions to create databases, modify security rules, etc.
| - 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 | - AI might execute destructive operations (e.g., deleting data) – review critical steps
- Local mode runs on your machine; code doesn't leave until you deploy, but cloud traffic uses HTTPS
- Hosted mode transmits SecretId/SecretKey over HTTP – ensure trusted environment
| - 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 Code, Cursor, Codex, Gemini CLI, OpenCode, WindSurf, Trae, Tongyi Lingma, RooCode, CLINE, GitHub Copilot, Baidu Comate, Augment Code, OpenClaw, WorkBuddy, ZCode, CodeBuddy | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 0 | 4 | 0 |
|---|