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.

DimensionBetterDB MCP ServerMCP observability for Valkey and RedisDBHubBytebase's official, minimalist two-tool database MCP server
FMRS55 / 100 · C74 / 100 · B
Reliability9 / 2013 / 20
Security and permissions10 / 2013 / 20
Maintenance11 / 2016 / 20
Documentation13 / 2015 / 20
Setup experience12 / 2017 / 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
  • 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 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 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 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 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
  • 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
  • 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, CursorClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools02