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 Aura Manager MCP ServerManage Neo4j Aura cloud instances in natural languageMCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS45 / 100 · D79 / 100 · B75 / 100 · B
Reliability8 / 2012 / 2012 / 20
Security and permissions7 / 2018 / 2016 / 20
Maintenance11 / 2017 / 2014 / 20
Documentation9 / 2017 / 2018 / 20
Setup experience10 / 2015 / 2015 / 20
Best for
  • Developers on Neo4j Aura who want to manage instances through a conversational assistant
  • Teams that need to quickly spin up or clean up test Aura instances
  • Users already running Claude Desktop or another MCP client
  • 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 the officially supported Neo4j product MCP server (use neo4j/mcp)
  • Production environments that require SLAs, backwards compatibility commitments, or a stable long-term API
  • Users who do not use Neo4j Aura
  • 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
  • Neo4j Aura API credentials (Client ID and Client Secret) that can create, modify, and delete Aura instances
  • Full administrative access to the user's Aura account
  • 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
  • The Aura API credentials are highly privileged; if leaked, another party could create, scale, or even delete instances, affecting billing and data availability
  • The model may misinterpret natural language instructions, leading to accidental instance deletion or unexpected scaling costs
  • As a Neo4j Labs experimental project, it may introduce breaking changes or deprecations with no compatibility guarantees
  • An exposed Client Secret in logs or client configuration can leak credentials
  • 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