Redis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_DB | No | Database number (0-15) | 0 |
| REDIS_TLS | No | Use TLS connection | false |
| REDIS_HOST | No | Redis host | localhost |
| REDIS_PORT | No | Redis port | 6379 |
| MCP_WEB_PORT | No | Web UI port | 3457 |
| REDIS_PASSWORD | No | Redis password | |
| REDIS_USERNAME | No | Redis username (for ACL) | |
| MCP_OPEN_BROWSER | No | Auto-open browser on start | true |
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_queryA | 执行只读 Redis 命令（GET / HGETALL / LRANGE / SMEMBERS / SCAN / INFO 等）。服务端按命令本身判定是否只读，写命令会被拒绝并提示改用 redis_execute。结果按 limit 截断。返回包含 connection / env / envLabel / readOnly / allowedOps / count / truncated / result。 |
| redis_executeA | 执行写入 / 删除 / 管理 / 高危命令（SET / HSET / DEL / EXPIRE / CONFIG / FLUSHALL 等）。这些命令会按当前连接的环境标识（测试库 / 正式库）对应的权限模板逐类校验，被禁类别在命令下发前就被拦下。返回包含 connection / env / envLabel / readOnly / allowedOps / operation / result。 |
| redis_contextA | 查看或切换上下文。不带参数：返回当前连接、环境标识、库序号、该环境放行的操作类别、已保存连接列表。传 database：切换到指定库序号（范围取自实例的 databases 配置）。传 connection：切换到已保存的连接并重新建连。切换只会影响当前 MCP 进程，不会改变连接的环境标识。 |
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 3 tools
The three tools have clearly distinct roles: redis_query is strictly read-only, redis_execute handles writes/deletes/admin/high-risk commands, and redis_context manages connection/database context. Boundary is reinforced by server-side read-only enforcement and rejection messages directing callers to the right tool.
All tools use the redis_ prefix and are readable, giving a predictable grouping. However, query and execute are verbs while context is a noun, so the convention is slightly mixed but still intuitive.
Three tools are well-scoped for a Redis MCP server: read, write/admin, and context management cover the main interaction modes without redundancy. Each tool earns its place and there is no obvious tool bloat.
The surface covers read-only queries, write/admin commands, and context switching/listing, which are the core Redis operations an agent needs. Minor gaps exist around saved-connection lifecycle management (create/delete saved connections) and possibly transaction/pipeline workflows, but agents can work around these.