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 languageMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS45 / 100 · D74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions7 / 2013 / 20
Maintenance11 / 2017 / 20
Documentation9 / 2016 / 20
Setup experience10 / 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 that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
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
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
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
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
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 tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsClaude Desktop, VS Code, Cursor, Windsurf, Gemini CLIClaude Code, Gemini CLI, Zed, Antigravity
Tools00