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 Aura Manager MCP ServerManage Neo4j Aura cloud instances in natural languageDBHubBytebase's official, minimalist two-tool database MCP server
FMRS45 / 100 · D74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions7 / 2013 / 20
Maintenance11 / 2016 / 20
Documentation9 / 2015 / 20
Setup experience10 / 2017 / 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
  • 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
  • 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 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
  • 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 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
  • 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
  • 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