← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionNeo4j Data Modeling MCP ServerCreate, validate, and visualize Neo4j graph data modelsMCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS51 / 100 · D79 / 100 · B75 / 100 · B
Reliability8 / 2012 / 2012 / 20
Security and permissions10 / 2018 / 2016 / 20
Maintenance13 / 2017 / 2014 / 20
Documentation9 / 2017 / 2018 / 20
Setup experience11 / 2015 / 2015 / 20
Best for
  • Neo4j users who want to design and validate graph models before committing them
  • Developers doing graph data modeling from MCP-compatible clients
  • 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
  • Teams requiring official Neo4j product support or SLAs
  • Production environments requiring backwards-compatibility guarantees
  • 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
  • Runs locally over stdio using local machine resources
  • 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
  • Neo4j Labs project with frequently updated experimental features and no guarantees around backwards compatibility or deprecation
  • Not supported by the Neo4j product team
  • Importing/exporting models from Arrows.app may send model data to an external service
  • 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 Desktop
Tools0427