M
MCP Directory CURATED DIRECTORY
863 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.

DimensionNeo4j Knowledge Graph Memory ServerPersonal knowledge graph memory stored in Neo4jMCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS59 / 100 · C79 / 100 · B75 / 100 · B
Reliability10 / 2012 / 2012 / 20
Security and permissions12 / 2018 / 2016 / 20
Maintenance14 / 2017 / 2014 / 20
Documentation11 / 2017 / 2018 / 20
Setup experience12 / 2015 / 2015 / 20
Best for
  • Users who already have a Neo4j instance (local or remote) and want an AI assistant to reuse memory
  • Developers who need knowledge and relationships preserved across sessions and clients
  • Users comfortable with experimental Neo4j Labs software and willing to absorb version-change risk
  • 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
  • Users looking for official Neo4j product support, SLAs, or backwards-compatibility guarantees
  • Users who have no Neo4j instance and do not want to deploy or maintain a database
  • Users who need Cypher query execution, Aura cloud instance management, or graph data modeling from this server (those are other servers in the same repository)
  • 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
  • Read and write nodes and relationships in the configured Neo4j database (for storing and retrieving memories)
  • Read NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, NEO4J_DATABASE, and NEO4J_NAMESPACE environment variables at runtime
  • 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 credentials live in the client configuration as environment variables; NEO4J_PASSWORD is secret and must be protected
  • Memories stored in the knowledge graph may be read during sessions, so sensitive or private content should be assessed beforehand
  • As a Neo4j Labs server it is experimental and may change incompatibly or drop features
  • Database read/write scope is determined by the supplied Neo4j account; overly broad permissions mean mistaken writes can affect other data in that database
  • 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 Desktop, VS Code, Cursor, Windsurf, Gemini CLIClaude DesktopClaude Desktop
Tools0427