MCP Redis Diagnostics

MCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations.

Why This Tool?

Most Redis MCP servers are CRUD wrappers (get/set keys). RedisNexus offers diagnostics but targets enterprises (K8s, multi-tenant SaaS). This tool is the only lightweight npm package for deep Redis diagnostics — 7 tools covering memory fragmentation, slowlog patterns, client connection health, keyspace distribution, latency analysis, and configuration auditing. Install with `npx`, no Docker or SaaS required.

Pro Tier

Generate exportable diagnostic reports (HTML + PDF) with a Pro license key.

• Full JVM thread dump analysis report with actionable recommendations
• PDF export for sharing with your team
• Priority support

$9.00/month — Get Pro License

Pro license key activates the `generate_report` MCP tool in mcp-jvm-diagnostics.

Tools (7)

`analyze_memory`

Analyze Redis memory usage and fragmentation.

Detects:

• High memory fragmentation (>1.5x RSS/used ratio)
• Swap risk (fragmentation 10ms, >100ms thresholds)
• Command concentration patterns
• Full slowlog buffer (missing history)

`analyze_clients`

Analyze Redis client connections.

Detects:

• Blocked clients (BLPOP/BRPOP)
• Connection pool saturation (>80% maxclients)
• Idle connections (>5 minutes)
• Large output buffer memory
• Pub/sub subscriber patterns

`analyze_keyspace`

Analyze Redis keyspace distribution and cache effectiveness.

Detects:

• Low TTL coverage ( Requires `latency-monitor-threshold` to be set in redis.conf (e.g., `CONFIG SET latency-monitor-threshold 100`).

`analyze_config`

Analyze Redis configuration for security and reliability risks.

Detects:

• No maxmemory limit (unbounded memory growth, OOM risk)
• Unsafe eviction policy (noeviction causing errors at memory limit)
• Network exposure (bind 0.0.0.0 without protected-mode)
• Missing authentication (no requirepass)
• Disabled persistence (both AOF and RDB off — data loss on restart)
• Idle connection accumulation (timeout 0)
• Disabled TCP keepalive (dead connections undetected)
• Low server frequency (hz "What's my cache hit rate? Are my TTLs configured properly?"

> "Give me a full Redis health check"

Part of the MCP Java Backend Suite

This tool is part of a suite of MCP servers for backend developers:

• mcp-db-analyzer — PostgreSQL/MySQL/SQLite schema analysis
• mcp-jvm-diagnostics — Thread dump and GC log analysis
• mcp-migration-advisor — Flyway/Liquibase migration risk analysis
• mcp-spring-boot-actuator — Spring Boot health and metrics analysis
• mcp-redis-diagnostics — Redis memory, slowlog, and client diagnostics

Limitations & Known Issues

• Single Redis instance: Analyzes one Redis instance at a time. Does not support Redis Cluster topology discovery or Sentinel failover analysis.
• ACL restrictions: Some tools require specific Redis commands (SLOWLOG, CLIENT LIST, LATENCY). Redis ACLs may block these. The `analyze_performance` unified tool handles partial failures gracefully.
• Latency monitoring: The `analyze_latency` tool requires `latency-monitor-threshold` to be set in redis.conf. Without it, no latency events are captured.
• Key-level analysis: Keyspace analysis uses `INFO keyspace` aggregates. Individual key inspection (e.g., finding the largest keys) requires `MEMORY USAGE` per key, which is not performed to avoid impacting production.
• Redis Cluster: No cluster-specific analysis (slot distribution, rebalancing, cross-node latency). Works against individual nodes only.
• Redis Modules: Module-specific commands and data types (RedisJSON, RediSearch, RedisTimeSeries) are not analyzed.
• Memory advisor: Memory recommendations are based on `INFO memory` stats. For detailed memory breakdown by key type, use `redis-cli --bigkeys` externally.
• Fragmentation ratio: Memory fragmentation uses RSS vs. used memory ratio, which can be distorted by jemalloc. Values <1.0 may not always indicate swapping.
• Read-only: All commands are read-only (INFO, SLOWLOG GET, CLIENT LIST, LATENCY). No data or configuration is modified.

License

MIT

End-of-life: 2026-05-10.

This MCP server is no longer maintained or distributed. The Corporation

has pivoted to Apify marketplace actors. See

`irrationalways` on Apify and

`irrcorp/bzp-poland-tenders` for current Corporation work.

The npm package has been unpublished. The repository is archived for

historical reference only.