mcp-redis-allowlist
Related Servers
Alternatives to mcp-redis-allowlist
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables exploring and diagnosing a Redis instance from MCP clients with read-only safety, using SCAN instead of KEYS for safe key enumeration.7122 npm2MIT
- AlicenseNot gradedqualityCmaintenanceA safe, connection-efficient Redis MCP server that provides tools for reading and managing Redis data, with safeguards like confirmation requirements for destructive operations.69 npmISC

Upstash Redis MCPofficial
AlicenseNot gradedqualityDmaintenanceLightweight MCP server for Redis that allows running any Redis command and searching Redis documentation. Supports multiple named databases with HTTP/REST or TCP transport.91 npmMIT- AlicenseAqualityCmaintenanceRead-only MySQL/MariaDB MCP server for running SELECT queries safely, with automatic read-only enforcement and query limits.39 npmMIT
- AlicenseBqualityBmaintenanceA read-only MCP server that provides diagnostic tools for MySQL performance troubleshooting, including processlist, lock waits, InnoDB status, and replication lag, without exposing generic SQL or application data.16MIT
- FlicenseNot gradedqualityBmaintenanceA read-only MCP server for observing registered local and SSH hosts, providing system, service, container, Git, and GPU status/log inspection through a closed-world registry without arbitrary shell access.-
TDQS
Scored across 5 tools
Most tools have distinct purposes: redis_get is for string keys, redis_inspect is a general inspection tool, redis_scan is for scanning, redis_info is for server info, and redis_command is a generic command runner. There is slight overlap between redis_get and redis_inspect for string key retrieval, but redis_inspect also provides more metadata and works on any key type.
All tools follow a consistent verb_noun pattern with 'redis_' prefix and an imperative verb (command, get, info, inspect, scan). No mixing of naming conventions.
5 tools is within the typical range for a focused Redis server, covering common read-only operations and inspection. It's slightly minimal but reasonable.
The tool set is heavily read-only, missing write operations (SET, DEL, update) and support for non-string data structures. This creates significant gaps for typical Redis usage workflows.