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.

DimensionDBMCP Database MCP ServerSingle-binary SQL database MCP server with built-in PII redaction and write-preventionMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS67 / 100 · C74 / 100 · B
Reliability9 / 2013 / 20
Security and permissions15 / 2013 / 20
Maintenance13 / 2017 / 20
Documentation17 / 2016 / 20
Setup experience13 / 2015 / 20
Best for
  • Users who need safe, read-only AI access to SQL databases
  • Teams with data-privacy requirements needing PII redaction
  • Developers wanting a zero-dependency, single-binary deployment
  • Environments using multiple database backends
  • 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 who cannot supply or configure database credentials
  • Users expecting unrestricted write access without understanding write-mode risks
  • Users of databases other than MySQL/MariaDB, PostgreSQL, or SQLite
  • 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
  • Requires database host, port, username, and password (DB_PASSWORD treated as a secret)
  • Read-only by default; disabling it lets the AI execute writes, and create/drop databases and tables
  • SSL/TLS connections require DB_SSL_CA/CERT/KEY certificate paths
  • Optional NER redaction requires a local ONNX model directory
  • 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
  • With read-only mode disabled, the AI can modify or delete data directly, including dropDatabase/dropTable
  • PII redaction is off by default; sensitive data in query results goes to the LLM unredacted unless enabled
  • Regex redaction is not foolproof, and ML/NER detection depends on model quality; v1 is English-only
  • HTTP mode may expose database access if allowed-origins/allowed-hosts are misconfigured
  • EXPLAIN ANALYZE actually executes the query, so beware of side effects and cost
  • 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, Cursor, Claude CodeClaude Code, Gemini CLI, Zed, Antigravity
Tools130