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.

DimensionNeo4j Cypher MCP ServerAn MCP server for running Cypher queries against a Neo4j database.DBHubBytebase's official, minimalist two-tool database MCP server
FMRS56 / 100 · C74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions11 / 2013 / 20
Maintenance13 / 2016 / 20
Documentation12 / 2015 / 20
Setup experience12 / 2017 / 20
Best for
  • Developers who already run a Neo4j instance and want to query it in natural language
  • Users of MCP clients such as Claude Desktop, VS Code, Cursor, Windsurf, or Gemini CLI
  • Teams looking to connect a graph database to LLM workflows
  • Users comfortable with lab-stage experimental features and self-supported maintenance
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
Not for
  • Production users who need official product support, SLAs, or backwards compatibility guarantees
  • Neo4j instances where the APOC plugin cannot be installed or enabled (schema inspection will not work)
  • Users who only want the officially supported Neo4j MCP server
  • Users without an accessible Neo4j instance or database credentials
  • Scenarios needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
Required permissions
  • Read the configured Neo4j database and its schema
  • Execute read and write Cypher queries on the configured Neo4j database
  • Access Neo4j credentials, including NEO4J_URI, NEO4J_USERNAME, and the sensitive NEO4J_PASSWORD
  • Requires a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
Risks and side effects
  • This is an experimental Neo4j Labs project with no SLAs or backwards compatibility guarantees, and it may change between versions
  • Write Cypher queries can be executed by default, potentially modifying or deleting data in the database
  • NEO4J_PASSWORD is sensitive and can leak if misconfigured
  • The server is not officially supported by the Neo4j product team
  • Deploying in HTTP/SSE mode on a network may expose the endpoint to unauthorized access
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude Desktop, VS Code, Cursor, Windsurf, Gemini CLIClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools02