M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← 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 assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS43 / 100 · D79 / 100 · B75 / 100 · B
Reliability6 / 2012 / 2012 / 20
Security and permissions8 / 2018 / 2016 / 20
Maintenance8 / 2017 / 2014 / 20
Documentation9 / 2017 / 2018 / 20
Setup experience12 / 2015 / 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.
  • Drug discovery and computational chemistry researchers
  • Bioinformatics teams needing ChEMBL data through AI assistants
  • Developers comfortable with Node.js or Docker
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.
  • 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 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.
  • 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
  • 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.
  • 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 clientsClaude DesktopClaude DesktopClaude Desktop
Tools9427