mcp-redis-allowlist
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_URL | Yes | Redis connection URL, e.g., redis://localhost:6379 | |
| REDIS_WRITE_ALLOWED | No | Set to 'true' to bypass the read-only guard (not recommended for production). Default is false. | false |
| REDIS_EXTRA_READONLY_COMMANDS | No | Comma or whitespace separated list of extra read-only command specs, e.g., 'client:list,slowlog:get,latency:latest' |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redis_getC | GET a string key and its TTL. |
| redis_scanB | Cursor-safe key scan by glob pattern using SCAN. |
| redis_inspectB | Inspect type, TTL, size, and a small preview for a key. |
| redis_commandB | Run an arbitrary Redis command restricted to the read-only allowlist unless writes are enabled. |
| redis_infoB | Run Redis INFO, optionally scoped to a section. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.