M
MCP Directory CURATED DIRECTORY
693 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.

DimensionBetterDB MCP ServerMCP observability for Valkey and RedisMCP ClickHouseConnect ClickHouse to your AI assistantsMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS55 / 100 · C79 / 100 · B74 / 100 · B
Reliability9 / 2012 / 2013 / 20
Security and permissions10 / 2018 / 2013 / 20
Maintenance11 / 2017 / 2017 / 20
Documentation13 / 2017 / 2016 / 20
Setup experience12 / 2015 / 2015 / 20
Best for
  • Teams needing Valkey 8.x monitoring with COMMANDLOG and CLUSTER SLOT-STATS
  • Operators needing Redis 6+ compatible monitoring, historical analytics, and audit trails
  • Users who already run BetterDB Monitor and want to query it through MCP
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
  • 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 seeking generic Redis write or administration operations without BetterDB Monitor
  • Users without an accessible Valkey or Redis instance
  • Users who need documented, tool-specific MCP calls when no tool identifiers are provided
  • Scenarios requiring write access to the database without explicit opt-in.
  • Production environments with stringent security requirements that avoid default permission settings.
  • 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
  • Access to the BetterDB Monitor instance URL is required
  • An MCP authentication token generated from the BetterDB Settings page is required
  • The Monitor requires connectivity to the target Valkey or Redis instance to collect monitoring data
  • Requires read-only access to ClickHouse database (default).
  • Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
  • Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
  • 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
  • MONITOR capture records live database traffic and may expose sensitive commands or data
  • Persistent audit, analytics, and capture data require an appropriate storage backend; memory storage loses data on restart
  • The MCP token is a sensitive credential and should be protected
  • Some advanced features require Pro or Enterprise licensing, although certain features are free during early access
  • If write access is enabled, AI might make unintended modifications.
  • If DROP access is enabled, data deletion could occur accidentally.
  • Credentials may be exposed via environment variables.
  • 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 Code, CursorClaude DesktopClaude Code, Gemini CLI, Zed, Antigravity
Tools040