del
Delete a key
LABSCO SUMMARY
Debugging a cache stops being a separate terminal session and becomes part of the same conversation.
This is a working client, not a viewer: del removes a key outright and set overwrites unless NX is passed, so an agent holding these tools can change whatever state the instance holds. The read paths are shaped for exactly the questions you ask during an incident — scan by pattern to find the key, hgetall to see the whole record, zrangebyscore to pull the slice of a leaderboard or queue that a score range covers. Expiry is available where it belongs, on set through PX, rather than as a separate tool.
What it is
A Redis client exposed as 13 tools, covering strings, hashes, sorted sets, sets and key discovery against one instance.
What you get
- Key discovery without dumping the keyspace: scan matches a pattern and takes a count to bound each pass.
- String values: get reads a key, set writes one with optional NX so it only lands if the key is absent and PX to attach an expiry in milliseconds, and del removes it.
- Hashes read whole or by field: hmset writes several fields at once, hget reads one, and hgetall returns every field and value.
- Sorted sets addressed both ways: zadd adds members, zrange returns a range by index, zrangebyscore returns members between a min and a max score, both optionally with scores, and zrem removes members.
- Plain sets: sadd adds members and smembers returns everything in the set.
Requirements
A Redis instance the host can reach, addressed by hostname and port when the server starts.
Setup effort
One command — npx redis-mcp --redis-host localhost --redis-port 6379
USE CASES
01
Chasing the cache key behind a bug report
Find the keys matching the pattern from the report, then read whichever shape they turn out to be.
02
Reading a leaderboard without opening a terminal
Page the sorted set by rank or pull the slice inside a score range, and drop members that should no longer be counted.
03
Seeding fixture state before a test run
Write the string, hash and set values the run expects, then read one back to confirm the shape is right.
04
Clearing a stuck lock or feature flag
Read what the key currently holds, then either delete it or overwrite it with a value that carries its own expiry.
13 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get
Get string value
hget
Get the value of a hash field
hgetall
Get all the fields and values in a hash
hmset
Set multiple hash fields to multiple values
sadd
Add one or more members to a set
scan
Scan Redis keys matching a pattern
set
Set string value with optional NX (only if not exists) and PX (expiry in milliseconds) options
smembers
Get all members in a set
zadd
Add one or more members to a sorted set
zrange
Return a range of members from a sorted set by index
zrangebyscore
Return members from a sorted set with scores between min and max
zrem
Remove one or more members from a sorted set
BEFORE YOU INSTALL
What to know first
Tools you get
13 tools when we connected. Six tools write, including del, which deletes keys, and there is no read-only switch. The names are bare Redis commands, so they can collide with other servers in the same client.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 13 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx redis-mcp --redis-host localhost --redis-port 6379MCP Clients
Claude Desktop, Cline
JSON
{
"mcpServers": {
"redis": {
"command": "npx",
"args": [
"redis-mcp",
"--redis-host",
"localhost",
"--redis-port",
"6379"
],
"disabled": false
}
}
}
