mcp-server-redis
Related Servers
Alternatives to mcp-server-redis
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI to safely view and operate Redis databases with read-only mode by default and support for key operations.11MIT
- AlicenseAqualityDmaintenanceEnables AI agents to manage and search data in Redis using natural language. Supports hashes, lists, sets, sorted sets, streams, JSON, and vector search.44MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to perform comprehensive Redis database operations including managing strings, hashes, lists, sets, sorted sets, TTL management, and data backup/restore. Supports secure connections and provides batch operations for efficient Redis interaction through natural language.345 npm2MIT
- AlicenseNot gradedqualityFmaintenanceProvides access to Redis databases. This server enables LLMs to interact with Redis key-value stores through a set of standardized tools.148 npm30MIT
- AlicenseAqualityAmaintenanceEnables exploring and diagnosing a Redis instance from MCP clients with read-only safety, using SCAN instead of KEYS for safe key enumeration.7200 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables clients to inspect and operate many Redis deployments at once — standalone, Redis Cluster, or Sentinel-managed — through a single endpoint, with 54 tools grouped into core, data, JSON, search, pub/sub, and docs toolsets. It supports read-only and destructive-tool switches, per-cluster isolation, secret-backed passwords, bounded 15-second calls, and Streamable HTTP or stdio transport.MIT
TDQS
Scored across 4 tools
The four tools are largely distinct: redis_execute_command is a broad gateway, while redis_inspect_key and redis_scan_keys are specialized. Overlap exists because execute_command can perform SCAN/TYPE/TTL, but specialized tools offer clearer safety and aggregation semantics.
All tools use the redis_ prefix and snake_case verb_noun naming (execute_command, list_connections, inspect_key, scan_keys). Consistent and predictable.
Four tools is slightly lean but well-scoped; the generic execute_command handles most Redis operations, so extra tools would be redundant. Specialized tools add safety and convenience without bloating the surface.
The set covers command execution (any Redis command, pipelines), key discovery (scan), key diagnostics (inspect), and connection listing. No obvious gaps for a Redis command gateway; lifecycle operations like connection management are minimal but consistent with the single-connection design.