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.

DimensionMySQL MCP ServerQuery MySQL databases through MCP with read-only defaults.DBHubBytebase's official, minimalist two-tool database MCP server
FMRS50 / 100 · D74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions10 / 2013 / 20
Maintenance9 / 2016 / 20
Documentation11 / 2015 / 20
Setup experience12 / 2017 / 20
Best for
  • Developers and data teams that need AI-assisted MySQL schema inspection or querying
  • Workflows that prefer read-only database access by default
  • Deployments requiring SSH, SSL/TLS, or PII-redaction capabilities
  • 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
  • Environments that do not use MySQL
  • Workflows requiring write access by default without explicit permission configuration
  • Environments unable to provide suitable database credentials or network connectivity
  • 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
  • Requires configuration for the MySQL host, port, username, password, and database name
  • The database user needs privileges matching the intended queries and any enabled write operations
  • Remote database access may require SSH tunnel configuration
  • When write flags are enabled, the server can perform the corresponding insert, update, or delete operations
  • 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
  • Although read-only by default, enabled write flags can modify or delete data
  • Database credentials are supplied through environment variables and should be protected
  • SQL queries may expose sensitive data; PII redaction can help reduce exposure
  • Misconfigured database privileges, SSL/TLS, or remote access may broaden data exposure
  • 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, Claude CodeClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools12