MCP SERVERRun the Redis health checks an operator would run — memory fragmentation, slowlog for O(N) commands, latency spikes from fork and AOF fsync, replication and configuration risk — as eight analyses rather than raw INFO output.
LABSCO SUMMARY
Redis exposes plenty of statistics and almost nobody knows which combinations mean trouble. High fragmentation with normal memory use, a slowlog full of KEYS, a latency chart that spikes exactly when a background save runs — those are recognisable to someone who has operated Redis and invisible in raw INFO output. Encoding that recognition into the tools means an agent returns a finding rather than a table for a human to interpret. The TTL coverage check is the quiet standout: a cache where most keys have no expiry is the failure that shows up as a memory alert months later, and nothing else surfaces it.
A diagnostic layer over Redis: seven focused analysers plus one that runs them all, each interpreting the server's own statistics rather than returning them.
REDIS_URL. Everything here reads — there is no tool that changes configuration or evicts anything.
One command — npx -y mcp-redis-diagnostics
USE CASES
Run every analyser at once and read the findings, rather than deciding in advance which subsystem is at fault.
Separate fork latency from RDB and AOF saves from AOF fsync stalls, and check whether clients are blocking.
Check fragmentation and RSS overhead against maxmemory, then look at whether keys have TTLs at all.
Read the slowlog for dangerous O(N) commands specifically — the ones that were fine when the keys were small.
Check the configuration for security and reliability risks and confirm replication is actually healthy.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
analyze_clientsAnalyze Redis client connections. Detects blocked clients, connection pool saturation, large output buffers, and pub/sub subscriber concentration. Idle connection count excludes replica (S flag) and pub/sub subscriber (P flag) connections, which are expected to be persistent — this prevents false positives when the target Redis instance has replicas or pub/sub consumers attached.
analyze_configAnalyze Redis configuration for security and reliability risks. Flags: no maxmemory limit, unsafe eviction policy (noeviction with maxmemory set), network exposure (bind 0.0.0.0 without authentication), no requirepass, disabled persistence (both AOF and RDB off), idle connection timeout not set, TCP keepalive disabled, server frequency (hz) too low, and latency-monitor-threshold disabled (which silences the analyze_latency tool).
analyze_keyspaceAnalyze Redis keyspace distribution. Checks TTL coverage, cache hit/miss rates, database distribution balance, and expiry patterns.
analyze_latencyAnalyze Redis latency events. Detects fork latency spikes (RDB/AOF), AOF fsync delays, slow command processing, eviction/expiry cycle delays, and active defragmentation impact. Requires latency-monitor-threshold to be set.
analyze_memoryAnalyze Redis memory usage. Detects high fragmentation, RSS overhead, maxmemory pressure, eviction issues, and swap risk. Provides actionable recommendations for memory optimization.
analyze_performanceComprehensive Redis health assessment. Runs all analyzers (memory, slowlog, clients, keyspace, latency, replication, config) and produces a unified report with prioritized recommendations.
analyze_replicationAnalyze Redis replication health. For masters: reports connected replica count, per-replica state (online/wait_bgsave/send_bulk) and lag in seconds, backlog size adequacy, and partial resync offset history. For replicas: detects broken master link, high I/O lag, and full sync in progress. Works for both master and replica roles.
analyze_slowlogAnalyze Redis SLOWLOG to find slow commands. Detects dangerous O(N) commands (KEYS, SMEMBERS, HGETALL, LRANGE, SORT, FLUSHDB, FLUSHALL), identifies latency hotspots, and recommends safer alternatives (SCAN, SSCAN, HSCAN, bounded ranges, sorted sets).
BEFORE YOU INSTALL
8 tools when we connected. All eight only read. analyze_latency returns nothing unless latency-monitor-threshold is set in redis.conf, and Redis ACLs can block the commands the slowlog and client analyzers use.
The documented client runs the server on your machine.
CONTEXT COST
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y mcp-redis-diagnostics{
"mcpServers": {
"redis-diagnostics": {
"command": "npx",
"args": [
"-y",
"mcp-redis-diagnostics"
],
"env": {
"REDIS_URL": "redis://localhost:6379"
}
}
}
}The author declared this project end-of-life on 2026-05-10 and no longer maintains it. The npm package mcp-redis-diagnostics is still published (0.1.14, May 2026) and npx still installs it, but no fixes or updates will follow.
MCP servers
neo4j-contrib
TyKolt
Akhilvis
instantdb