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
B
55FMRS · C
The supplied material identifies BetterDB Inc. as the maintainer, the @betterdb/mcp npm package, and stdio transport. The server is suited to querying BetterDB Monitor's Valkey and Redis observability data through MCP. No individual tool identifiers are included in the source, so the tool list is empty.
BetterDB MCP Server exposes BetterDB Monitor's Valkey and Redis observability capabilities to Claude Code, Cursor, and other MCP clients. It covers historical analytics, slowlog and COMMANDLOG data, MONITOR captures, hot keys, cluster visibility, client analytics, ACL audits, Prometheus metrics, and migration observability.
Tools
The tool list has not been reviewed yet.
Setup
Run the server over stdio with npx @betterdb/mcp. Set BETTERDB_URL to the BetterDB Monitor instance and set BETTERDB_TOKEN to an MCP token generated in the BetterDB Settings page. Set BETTERDB_INSTANCE_ID for multi-instance cloud deployments. Alternatively, use --autostart to start a local Monitor process; --port selects the API port, defaulting to 3001, and storage can be sqlite or memory.
claude_desktop_config.json
{"command":"npx","args":["@betterdb/mcp"],"env":{"BETTERDB_URL":"http://localhost:3001","BETTERDB_TOKEN":"your-mcp-token","BETTERDB_INSTANCE_ID":"your-instance-id"}}
Fit and risk
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
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
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
Troubleshooting
- Verify that Node.js is at least version 20.0.0
- Verify that BETTERDB_URL points to a reachable Monitor API
- Verify that the token was generated in BetterDB Settings and check BETTERDB_INSTANCE_ID for multi-instance deployments
- Verify that Monitor is running and that its port matches the configuration; the default API port is 3001
- When using --autostart, check the port, storage option, and local Valkey or Redis connectivity
Use cases
Query historical slowlogs, command patterns, client activity, and latency for Valkey or Redis
Capture, filter, replay, and export live MONITOR traffic
Analyze hot keys, cluster slots, CPU and I/O threads, and ACL access records
Use BetterDB monitoring data with Prometheus, AI application traces, and incident investigations
Supported clients
Claude CodeFull support
CursorFull support