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.

DimensionDbxQuery and manage 70+ databases from AI agents via connections already configured in DBXDBHubBytebase's official, minimalist two-tool database MCP server
FMRS57 / 100 · C74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions10 / 2013 / 20
Maintenance14 / 2016 / 20
Documentation13 / 2015 / 20
Setup experience12 / 2017 / 20
Best for
  • Developers already using DBX desktop, web, or Docker with connections configured
  • Teams working across many different database engines who want one consistent MCP access point
  • Users who want a lightweight (20 MB) client without Java or Python runtime dependencies
  • 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 without an existing DBX installation or configured connections, since the MCP server itself does not manage new database credentials — it relies on connections already set up in DBX
  • Users who specifically need an MCP server maintained by a database vendor (e.g. the MySQL, PostgreSQL, or MongoDB projects themselves) rather than DBX's own client wrapper
  • Environments with strict no-write automation requirements where operators cannot verify the current DBX centralized MCP access-mode policy
  • 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
  • Access to database connection credentials already configured in DBX
  • Ability to execute SQL according to the mode selected in DBX Settings → MCP (read_only / safe_write / high_risk_write)
  • DBX_WEB_URL (and DBX_WEB_PASSWORD if password login is enabled) for Web/Docker deployments
  • DBX_DATA_DIR pointing to the data directory containing dbx.db for Windows portable builds
  • Node.js >= 18 when run via npx (or use the Node-free precompiled native binary instead)
  • 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
  • If the access mode is set to Data read/write or Full access, the AI agent can modify or delete data in connected databases
  • Insufficiently reviewed AI-generated SQL could execute unintended write operations against production databases
  • The legacy DBX_MCP_ALLOW_WRITES=0 environment variable only enforces read-only behavior until a central MCP policy has been saved for the first time — after that it no longer applies, so operators must track policy state
  • DBX_WEB_PASSWORD is stored in plaintext in client configuration, so config files should be protected
  • 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 Code, Cursor, WindsurfClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools02