| FMRS | 59 / 100 · C | 79 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 18 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 17 / 20 | 14 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 | 18 / 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.
| - Drug discovery and computational chemistry researchers
- Bioinformatics teams needing ChEMBL data through AI assistants
- Developers comfortable with Node.js or Docker
|
|---|
| 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.
| - Production settings requiring official ChEMBL support (this is unofficial)
- Users without a Node.js or Docker environment
- General database tasks unrelated to ChEMBL
|
|---|
| 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.
| - Outbound network access to https://www.ebi.ac.uk/chembl/api/data
- Read-only access to public API data; no authentication credentials required
|
|---|
| 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.
| - Unofficial project with license marked NOASSERTION (README claims MIT); verify licensing yourself
- Data accuracy depends on the ChEMBL REST API and the server's parsing may contain defects
- 30-second request timeouts may constrain large batch queries
- README inconsistency on tool count (22 vs 27) raises documentation reliability concerns
|
|---|
| Supported clients | Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Windsurf, Trae, Tongyi Lingma, Roo Code, Cline, GitHub Copilot, Baidu Comate, Augment Code, OpenClaw, WorkBuddy, ZCode, CodeBuddy | Claude Desktop | Claude Desktop |
|---|
| Tools | 0 | 4 | 27 |
|---|