# BetterDB-inc/monitor [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/BetterDB-inc/monitor  
**GitHub Stars:** 1308  
**npm Downloads (last month):** 1624  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/betterdb-inc-monitor

## Description
Valkey-first observability with Redis compatibility. Query real-time metrics, analyze slow commands, detect hot keys, and investigate performance issues directly from AI coding assistants.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "monitor": {
    "command": "npx",
    "args": ["-y","@betterdb/monitor"]
  }
}
```

## Documentation

## What BetterDB-inc/monitor does

BetterDB-inc/monitor connects AI assistants to the monitoring layer provided by BetterDB Monitor. The MCP package exposes 60 tools for inspecting Valkey and Redis behavior, including current metrics, historical slowlogs, command patterns, client activity, latency, hot keys, and cluster information.

The server is intended for operational investigation through an MCP-compatible client. An agent can use it to examine performance symptoms, identify services or commands associated with activity, and work with the monitoring data retained by BetterDB rather than relying only on a database’s current state.

## How it works

The MCP server runs as a stdio process through the `@betterdb/mcp` package. It communicates with an MCP client, such as Claude Code or Cursor, and obtains observability information from a BetterDB Monitor instance. BetterDB Monitor in turn monitors Valkey or Redis databases and provides the web UI, REST API, Prometheus endpoint, and MCP interface.

The available monitoring scope depends on the connected BetterDB deployment and database. Valkey 8.x receives native support for features such as COMMANDLOG, cluster SLOT-STATS, and per-thread I/O metrics. Redis 6 and later are supported for the compatible feature set.

## Setup and configuration

Start the MCP process with:

```bash
npx @betterdb/mcp
```

Create an MCP token in BetterDB Monitor under **Settings → MCP Tokens**. Tokens are required when using BetterDB Cloud and optional for self-hosted deployments. Configure the resulting MCP server in the client of your choice using that client’s standard MCP setup process.

The monitoring application itself can be launched with Docker, Helm, or the `@betterdb/monitor` CLI. For example, the Docker image exposes the dashboard on port 3001, while the CLI requires Node.js 20 or newer and can use SQLite, PostgreSQL, or in-memory storage for its history. Those deployment choices belong to BetterDB Monitor rather than to the MCP process.

## Tools and capabilities

The toolset can expose monitoring data and investigation workflows such as:

- Querying real-time and historical metrics.
- Reviewing slow commands, command patterns, and latency over selected time ranges.
- Finding frequently accessed hot keys and examining key analytics where enabled.
- Inspecting client activity and attributing behavior by client name and pattern.
- Viewing cluster topology, slot heatmaps, per-slot CPU, and key distribution.
- Examining CPU and I/O thread metrics on Valkey deployments that support them.
- Investigating ACL access history and persisted monitoring events.
- Working with vector-search and AI-related observability data where the connected deployment provides those features.

## Limitations and notes

Feature availability varies by database engine and version. Valkey 8.x has native capabilities that are unavailable in equivalent Redis tooling, while Redis 6+ support covers the compatible feature set. Some BetterDB capabilities, including anomaly detection, inference latency, semantic cache intelligence, and certain key analytics, are marked Pro and are free during early access.

The MCP server exposes BetterDB’s monitoring data; it is not a general-purpose replacement for direct Redis or Valkey command execution. A BetterDB Monitor deployment must be available for the MCP package to provide data, and cloud use requires a token.

_Full upstream README: https://allmcps.com/mcp/betterdb-inc-monitor/readme_

