← 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 assistants
FMRS51 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance13 / 2017 / 20
Documentation9 / 2017 / 20
Setup experience11 / 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.
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.
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.
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.
Supported clientsClaude Desktop
Tools04