Monitor MCP Server

BetterDB MCP server - Valkey observability for Claude Code and other MCP clients

Local serverstdioPython

What is the Monitor MCP server?

BetterDB MCP server - Valkey observability for Claude Code and other MCP clients. That is what the monitor mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A monorepo application for monitoring Valkey/Redis databases with a NestJS backend and React frontend.

The tools it exposes

The server publishes 10 tools. What each one is for:

  • Package — Language
  • Caching — The Caching tool exposed by this server
  • Tools — The Tools tool exposed by this server
  • Benchmarking — The Benchmarking tool exposed by this server
  • Backend — The Backend tool exposed by this server
  • Frontend — The Frontend tool exposed by this server
  • Monorepo — The Monorepo tool exposed by this server
  • Prerequisites — The Prerequisites tool exposed by this server
  • Installation — 2. Copy environment variables: bash cp .env.example .env
  • Requirements — The Requirements tool exposed by this server

What it needs from you

Configuration is passed through the environment: STORAGE_URL, BETTERDB_LICENSE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js >= 20.0.0 - pnpm >= 9.0.0 - Docker (for local Valkey or Redis instances)

Getting it running

@betterdb/monitor on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Monitor's toolset — Package, Caching, Tools and 7 more — is a fair guide to whether it matches your workflow. It is maintained by BetterDB-inc; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Monitor.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
PackageLanguage
CachingThe Caching tool exposed by this server.
ToolsThe Tools tool exposed by this server.
BenchmarkingThe Benchmarking tool exposed by this server.
BackendThe Backend tool exposed by this server.
FrontendThe Frontend tool exposed by this server.
MonorepoThe Monorepo tool exposed by this server.
PrerequisitesThe Prerequisites tool exposed by this server.
Installation2. Copy environment variables: bash cp .env.example .env
RequirementsThe Requirements tool exposed by this server.

How to install the Monitor MCP server

{
  "mcpServers": {
    "monitor": {
      "command": "npx",
      "args": ["-y", "@betterdb/monitor"],
      "env": {
        "STORAGE_URL": "your-value",
        "BETTERDB_LICENSE_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js >= 20.0.0 - pnpm >= 9.0.0 - Docker (for local Valkey or Redis instances)
VariableDescriptionRequired
STORAGE_URLEndpoint or connection string the server talks to.Yes
BETTERDB_LICENSE_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Monitor to Package.
  • Use Monitor to Caching.
  • Use Monitor to Tools.

Frequently asked questions

It connects Monitor to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (Package, Caching, Tools, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Monitor directly.