| FMRS | 53 / 100 · D | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 3 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 14 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 15 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 15 / 20 |
|---|
| Best for | - Teams already using the kintone platform who want an AI assistant to operate on apps and records
- Administrators who need to bulk-maintain kintone fields, forms, or general settings
- Developers who want to drive kintone REST API operations via natural language
| - 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 do not use the kintone platform
- Scenarios requiring access to apps inside kintone guest spaces (unsupported)
- Bulk record imports that need to set attachment field contents directly (unsupported)
| - 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 | - A kintone login username and password, or API token(s) (up to 9, comma-separated)
- Optional Basic auth username and password
- Optional client certificate (PFX file and password) for secure-access domains
- Actual app access depends on the View/Add/Edit/Delete kintone permissions granted to the account or token used
| - 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 | - The server can directly call the kintone REST API to add, update, and delete records, fields, and app settings, so mistakes can cause data loss or broken app configurations
- Credentials (password, API token, client certificate password) are passed via command-line arguments or environment variables, so config files and env vars must be protected from exposure
- Guest space apps are not supported, which can cause access issues if business processes rely on them
- The README states this server is outside kintone's official API support channel; issues must be reported via GitHub Issues
| - 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, Cursor | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 26 | 4 | 0 |
|---|