M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
B

BetterDB MCP Server

Official
MCP observability for Valkey and Redis
How to install ↓ Compare GitHub source repository ↗
Category
Database #31 of 58
Stars
★ 1.3k Very popular
Transport
stdio (local process)
Runtime
Node.js 20+ · Docker
Credentials
Optional API key
License
Other / unspecified
Last commit
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.

Strongest · Documentation 13/20 Weakest · Reliability 9/20

Reliability
9/20
Security and permissions
10/20
Maintenance
11/20
Documentation
13/20
Setup experience
12/20
Why each score
Reliability 9/20
The manifest identifies an npm stdio package, version, and startup arguments, while the README describes the MCP entry point and its BetterDB monitor dependency, making the happy path plausible. However, no MCP initialization, tool-list handshake, key-path tests, or actual CI contents are provided; the claim of 60 tools lacks per-tool evidence, and auto-start, persisted processes, and external database dependencies have unverified failure boundaries. Under the static calibration, the evidence does not support a score above 12.
Security and permissions 10/20
BETTERDB_TOKEN is marked secret, and the README documents offline licensing and telemetry disabling, showing some awareness of credential and network boundaries. However, the MCP can expose monitoring data, ACL audits, traffic capture, replay, export, and migration capabilities; there is no evidence of tool-level permissions, data scoping, sensitive-data handling, dangerous-operation confirmation, or a complete outbound data-flow disclosure. The supplied material does not establish a red-line risk, so the score is not reduced to 4 or below.
Maintenance 11/20
The repository is not archived and provides version 1.4.0, a named public maintainer, an MIT license statement, and an API-tests GitHub Actions badge, indicating maintenance activity. Still, only stars and open-issue count are supplied; there is no commit cadence, dependency-update policy, vulnerability-response channel, release process, or actual test result. The repository metadata says NOASSERTION, and the license information is inconsistent.
Documentation 13/20
The README covers Docker, CLI, database versions, storage, environment variables, licensing, air-gapped deployment, Prometheus, the API, and several operating examples. Points are deducted because it lacks an MCP tool catalog, per-tool parameters and return values, a permission model, limits, error troubleshooting, complete mainstream-client configuration examples, and cost information; package and badge naming is also somewhat inconsistent.
Setup experience 12/20
The README gives Node.js requirements, npx/global npm installation, the BetterDB URL, and token source, while the manifest lists stdio transport, arguments, and environment variables. This provides a workable baseline path, but users must prepare and configure a monitor instance and database; there is no complete Claude Code, Cursor, or other mainstream-client configuration example, nor evidence of a verified handshake or platform-specific behavior.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkConnects to a database

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

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

Setup

Before you start

Runtime：Node.js 20+ · Docker

BETTERDB_TOKEN optionalsecret MCP authentication token generated from the BetterDB web UI under Settings → MCP Tokens
Other optional settings (2)
BETTERDB_URL optional URL of the BetterDB monitor instance, e.g. http://localhost:3001 for a local Docker/CLI deployment
BETTERDB_INSTANCE_ID optional Instance ID to target when using multi-instance cloud deployments

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.

.mcp.json 
{"command":"npx","args":["@betterdb/mcp"],"env":{"BETTERDB_URL":"http://localhost:3001","BETTERDB_TOKEN":"your-mcp-token","BETTERDB_INSTANCE_ID":"your-instance-id"}}

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "command": "npx",
  "args": [
    "@betterdb/mcp"
  ],
  "env": {
    "BETTERDB_URL": "http://localhost:3001",
    "BETTERDB_TOKEN": "your-mcp-token",
    "BETTERDB_INSTANCE_ID": "your-instance-id"
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Generate and validate client config

Check that it works

Start the monitor with docker run -d --name betterdb -p 3001:3001 betterdb/monitor:latest, generate an MCP token under Settings → MCP Tokens, then confirm BetterDB's monitoring tools (60 per the README) appear in your MCP client's tool list, or ask for the current slowlog to prove the connection works.

Troubleshooting

  1. Verify that Node.js is at least version 20.0.0
  2. Verify that BETTERDB_URL points to a reachable Monitor API
  3. Verify that the token was generated in BetterDB Settings and check BETTERDB_INSTANCE_ID for multi-instance deployments
  4. Verify that Monitor is running and that its port matches the configuration; the default API port is 3001
  5. When using --autostart, check the port, storage option, and local Valkey or Redis connectivity

Things to try

Once connected, you can ask your AI assistant things like:

  • Show the slowlog queries and command patterns from the last hour
  • Summarize client activity and which service is causing the load
  • List recent anomaly events with their plain-English diagnoses
  • Show the cluster topology and hot keys by access frequency

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 Code
Cursor

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Compare with other MCP servers

Source revision c9043aed237c Data synced 2026-10-12 Read the FMRS scoring method