← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionNocoDB MCP ServerMCP server for interacting with NocoDB databases via natural language.MCP ClickHouseConnect ClickHouse to your AI assistants
FMRS43 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance8 / 2017 / 20
Documentation9 / 2017 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers who want to interact with NocoDB using natural language.
  • Users needing quick CRUD operations on NocoDB tables.
  • Scenarios integrating with AI assistants via MCP.
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
Not for
  • Not suitable for databases other than NocoDB.
  • Not ideal for complex transactional or advanced query requirements.
  • Not recommended for production environments with high security needs, as this fork is not officially maintained.
  • Scenarios requiring write access to the database without explicit opt-in.
  • Production environments with stringent security requirements that avoid default permission settings.
Required permissions
  • Requires NocoDB instance URL, API token, and Base ID.
  • Uses NocoDB API, requiring appropriate read/write permissions.
  • Requires read-only access to ClickHouse database (default).
  • Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
  • Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
Risks and side effects
  • API tokens may be exposed; store them securely.
  • Third-party fork may not be security audited.
  • Misuse could lead to permanent data deletion or overwrite.
  • 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.
Supported clientsClaude DesktopClaude Desktop
Tools94