mcp-redis-diagnostics
Related Servers
Alternatives to mcp-redis-diagnostics
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceA Model Context Protocol (MCP) server for Redis. Connect to any Redis instance and execute queries through AI assistants.30-
- AlicenseNot gradedqualityBmaintenanceMCP server enabling AI agents to design and deploy WRedis/Redis-backed services using expert patterns, architecture scaffolding, and a unified CLI.MIT

Upstash Redis MCPofficial
AlicenseNot gradedqualityCmaintenanceLightweight MCP server for Redis that allows running any Redis command and searching Redis documentation. Supports multiple named databases with HTTP/REST or TCP transport.46 npmMIT
Redis MCP Serverofficial
AlicenseBqualityAmaintenanceThe official Redis MCP Server is a natural language interface designed for agentic applications to efficiently manage and search data in Redis.534,224 PyPI617MIT- AlicenseBqualityCmaintenanceMCP server that exposes Redis API to AI models44MIT
- FlicenseAqualityDmaintenanceAI-powered MCP server for enterprise OpenShift/Kubernetes cluster management, providing diagnostic tools, RAG knowledge retrieval, and autonomous remediation recommendations.9-
TDQS
Scored across 8 tools
Each tool targets a distinct Redis diagnostic subsystem (memory, slowlog, clients, keyspace, latency, config, replication), with no overlap. The aggregate tool analyze_performance explicitly combines the others, removing any ambiguity about which to call.
All tools follow the same verb_noun pattern using the prefix 'analyze_' followed by a clear domain noun (e.g., memory, slowlog, clients). This uniform convention makes the tool names predictable and easy to distinguish.
Eight tools is well-scoped for a Redis diagnostics server, covering the essential health-check areas without redundancy or bloat. Each tool earns its place, and the aggregate adds value without muddying the scope.
The tool set comprehensively covers the major Redis diagnostic dimensions: memory, slowlog, clients, keyspace, latency, config, and replication, plus an integrated report. There are no obvious gaps for a diagnostics-focused server; the config analyzer even addresses the prerequisite for latency monitoring.