1. Conduid
  2. Healthcare
  3. Redis Diagnostics
MCP server · Healthcare

Redis Diagnostics

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

37Low

Scored 6 months ago · breakdown

About Redis Diagnostics

Redis Diagnostics is an MCP server in the Healthcare category: mCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations.

Install

Claude Code
claude mcp add redis-diagnostics -- npx -y mcp-redis-diagnostics
npx
npx -y mcp-redis-diagnostics

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (8)

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.

Parameters not published.

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

Parameters not published.

analyze_keyspaceAnalyze Redis keyspace distribution. Checks TTL coverage, cache hit/miss rates, database distribution balance, and expiry patterns.

Parameters not published.

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.

Parameters not published.

analyze_memoryAnalyze Redis memory usage. Detects high fragmentation, RSS overhead, maxmemory pressure, eviction issues, and swap risk. Provides actionable recommendations for memory optimization.

Parameters not published.

analyze_performanceComprehensive Redis health assessment. Runs all analyzers (memory, slowlog, clients, keyspace, latency, replication, config) and produces a unified report with prioritized recommendations.

Parameters not published.

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.

Parameters not published.

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

Parameters not published.

Ask AI

✦

Ask AI about Redis Diagnostics

Powered by Claude · Grounded in docs

I know everything about Redis Diagnostics. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

npm version

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 <1.0)
  • Maxmemory pressure (approaching limit)
  • Eviction patterns
  • Missing maxmemory configuration
  • Unsafe noeviction policy

analyze_slowlog

Analyze Redis SLOWLOG for slow commands.

Parameters:

  • count (number, default: 128) — Number of slowlog entries to retrieve

Detects:

  • Dangerous O(N) commands: KEYS, SMEMBERS, HGETALL, SORT
  • High latency commands (>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 (<20% of keys)
  • Low cache hit rate (<80%)
  • Unbalanced database distribution
  • High expiry/eviction rates
  • Multiple database anti-pattern

analyze_latency

Analyze Redis latency events from the LATENCY subsystem.

Detects:

  • Fork latency spikes (RDB/AOF background save blocking operations)
  • AOF fsync delays and write latency
  • Slow command processing (O(1) commands unexpectedly slow)
  • Eviction and key expiry cycle delays
  • Active defragmentation impact
  • Increasing latency trends over time

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 < 10 slowing background tasks)

analyze_performance

Comprehensive health assessment — runs all analyzers and produces a unified report.

Parameters:

  • slowlog_count (number, default: 128) — Number of slowlog entries

Installation

npm install -g mcp-redis-diagnostics

Or run directly:

npx mcp-redis-diagnostics

Configuration

Environment Variables

Variable Description Default
REDIS_URL Redis connection string redis://localhost:6379

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "redis-diagnostics": {
      "command": "npx",
      "args": ["-y", "mcp-redis-diagnostics"],
      "env": {
        "REDIS_URL": "redis://localhost:6379"
      }
    }
  }
}

Redis with password:

{
  "env": {
    "REDIS_URL": "redis://:yourpassword@localhost:6379"
  }
}

Quick Demo

Once configured, try these prompts in Claude:

  1. "Analyze my Redis memory usage — is there fragmentation?" — Shows used vs max memory, fragmentation ratio, eviction policy, and memory pressure issues
  2. "Check the Redis slowlog for dangerous commands" — Identifies O(N) commands like KEYS/SMEMBERS, high-latency patterns, and optimization suggestions
  3. "Run a complete Redis health check" — Unified report combining memory, slowlog, clients, keyspace, and latency analysis

"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

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Redis Diagnostics

How do I install Redis Diagnostics?

Run claude mcp add redis-diagnostics -- npx -y mcp-redis-diagnostics, then add the server to your MCP client's configuration.

Is Redis Diagnostics safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Redis Diagnostics still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.