← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionNeon MCP ServerInteract with your Lakebase Postgres databases on Neon using natural language.DBHubBytebase's official, minimalist two-tool database MCP server
FMRS73 / 100 · B74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions16 / 2013 / 20
Maintenance18 / 2016 / 20
Documentation17 / 2015 / 20
Setup experience14 / 2017 / 20
Best for
  • Developers and non-developers who want to manage Neon databases via natural language.
  • Users who want to perform database tasks quickly within IDEs or chat interfaces.
  • Teams needing safe migrations and query optimization.
  • 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 environments requiring fine-grained control.
  • Users needing a full SQL interface and complex transaction handling.
  • Users who want to run fully offline or without depending on remote services.
  • 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
  • Neon account and authentication (OAuth or API key).
  • Access, create, modify, and delete Neon projects, branches, databases, and resources.
  • Execute SQL queries (read/write).
  • Manage authentication and Data API configurations.
  • Read logs and documentation index.
  • 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
  • Natural language requests may accidentally execute destructive operations (e.g., deleting projects or branches).
  • Unauthorized individuals may access your account via API key or OAuth.
  • Production use carries risk of accidental changes; official recommendation is for local development only.
  • Careful review of LLM-proposed actions is required.
  • 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, Cursor, VS Code, Claude Code, KiroClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools342