Monitor
Pull Valkey instance health and observability from BetterDB into Claude Code when you run Redis-compatible caches in production.
Overview
BetterDB Monitor MCP is an MCP server for the Operate phase that connects agents to BetterDB Valkey observability over authenticated stdio tools.
What is this MCP server?
- BetterDB MCP server for Valkey observability aimed at Claude Code and other MCP clients
- npm package @betterdb/mcp (monitor repo packages/mcp) with stdio transport
- Auth via BETTERDB_TOKEN from BetterDB Settings plus BETTERDB_URL for the monitor instance
- BETTERDB_INSTANCE_ID for selecting targets in multi-instance cloud deployments
- npm package @betterdb/mcp (monitor packages/mcp, schema version 0.1.4)
- Valkey-focused observability per server description
- Three documented env vars: BETTERDB_URL, BETTERDB_TOKEN, BETTERDB_INSTANCE_ID
Community signal: 1.1k GitHub stars.
What problem does it solve?
When Valkey misbehaves in production, jumping between dashboards and logs breaks the flow of debugging with your AI coding agent.
Who is it for?
Indie SaaS operators already on BetterDB who want MCP-native cache observability during incidents and tuning.
Skip if: Builders without Valkey or BetterDB, or teams that only need local Redis on a laptop with no monitor deployment.
What do I get? / Deliverables
After you connect BETTERDB_URL and BETTERDB_TOKEN, your agent can query BetterDB monitor data for Valkey instances, including multi-instance cloud targets.
- Stdio MCP server wiring your agent to BetterDB Valkey observability APIs
- Authenticated monitor access without leaving the coding agent session
- Multi-instance targeting for cloud Valkey operations
Recommended MCP Servers
Journey fit
Canonical shelf is Operate because BetterDB Monitor is aimed at live Valkey observability after your app is deployed, not at initial feature coding. Monitoring matches MCP-driven inspection of cache instances, tokens, and multi-instance cloud targets rather than schema design.
How it compares
Valkey observability MCP connector, not a database migration skill or generic log aggregator.
Common Questions / FAQ
Who is BetterDB Monitor MCP for?
It is for operators using BetterDB to watch Valkey who want Claude Code or another MCP client to read monitor-backed observability context.
When should I use BetterDB Monitor MCP?
Use it in Operate monitoring when you diagnose cache performance, verify instance health, or compare multi-instance cloud targets after ship.
How do I add BetterDB Monitor MCP to my agent?
Install @betterdb/mcp from npm, set BETTERDB_URL and BETTERDB_TOKEN (and BETTERDB_INSTANCE_ID if needed), then register the stdio server in your MCP client.