Monitor logo

Monitor

by BetterDB-inc

MCP tools for querying BetterDB monitoring data from Valkey and Redis instances.

Install Monitor

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "betterdb-inc-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/monitor"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

BetterDB-inc/monitor exposes BetterDB’s observability data to AI assistants through the Model Context Protocol. Its 60 tools cover real-time metrics, historical analytics, slow commands, hot keys, client activity, cluster state, and performance investigations for Valkey and Redis. Run the MCP package with npx and connect it to a BetterDB Monitor deployment; cloud deployments require an MCP token, while self-hosted deployments can use one optionally. Reach for it when an agent needs database monitoring context instead of direct application-code access alone.

Use cases

  • Query historical latency and slow-command data during incident analysis
  • Find hot keys and inspect access patterns
  • Identify clients responsible for database activity
  • Review cluster topology and slot-level performance
  • Investigate Valkey or Redis behavior from an AI coding assistant

Key features

  • 60 MCP tools for BetterDB observability
  • Real-time and historical metric queries
  • Slow-command, hot-key, and client analytics
  • Valkey cluster and per-thread performance visibility
  • ACL activity and monitoring history access
  • Vector-search and AI observability data access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

54/54 checks healthy over the last 94d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @betterdb/monitor (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1.3kStargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Monitor works

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:

Terminal
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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Monitor

BetterDB-inc/monitor is an MCP server that connects AI assistants to BetterDB Monitor for Valkey and Redis observability. Its 60 tools query metrics, historical slowlogs, command patterns, client activity, hot keys, cluster state, latency, ACL history, and related performance data through an MCP-compatible client such as Claude Code or Cursor.

Run `npx @betterdb/mcp` to start the stdio MCP process. Add it to your MCP client using that client’s normal server configuration, then provide a token created under BetterDB Monitor’s Settings → MCP Tokens. Cloud deployments require the token; self-hosted deployments can use one optionally.

Yes, BetterDB-inc/monitor works with Cursor through its standard MCP support. Start the server with `npx @betterdb/mcp` and configure the process in Cursor. The server then exposes BetterDB monitoring tools for connected Valkey or Redis instances.

BetterDB-inc/monitor monitors Valkey and Redis through BetterDB Monitor. Valkey 8.x has native support for features including COMMANDLOG, cluster SLOT-STATS, and per-thread I/O metrics, while Redis 6 and later are supported for the compatible feature set.

A token is required for BetterDB Cloud and optional for self-hosted BetterDB deployments. Create one in BetterDB Monitor under Settings → MCP Tokens, then make it available through your MCP client’s configuration.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMonitor AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/betterdb-inc-monitor?style=directory)](https://allmcps.com/mcp/betterdb-inc-monitor)
HTML Embed
<a href="https://allmcps.com/mcp/betterdb-inc-monitor"><img src="https://allmcps.com/api/badge/betterdb-inc-monitor?style=directory" alt="Monitor on AllMCPs" /></a>