Full read-write Claude connector for Redis
Let Claude set keys, manage queues, and clear cache against your Redis instance
Stop dropping into a redis-cli session for routine cache and queue work. Claude reads and writes keys directly against your live instance, applies TTLs, and pushes or pops from queues, with destructive commands waiting on your approval.
Redis is an in-memory data store used as a cache, session store, queue, and key-value database. Teams want Claude to do more than describe keys: to read values, set and expire them, and manage queues directly against a live instance.
What is a Redis MCP server?
A Redis MCP server is a small hosted service that exposes Redis's data and actions to Claude over the Model Context Protocol, so Claude can records, tables, and queries inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Redis's current connector do today?
Redis does publish an official MCP server, but it ships a fixed, generic tool set that is not shaped to your instance or workflow. A custom connector gives you the full capabilities your team needs: scoped ACL users, per-command separation of reads and writes, confirmation gates on destructive commands, and the queue and cache patterns your work actually runs.
What does full read-write Redis access unlock?
Full read-write Redis access lets Claude set and update keys, apply TTLs and expirations, push to or pop from lists, manage hashes and sorted sets, and clear stale cache entries against a live instance. The cache and queue work that used to mean a redis-cli session happens through Claude, with approval on destructive commands.
- Set or update a key with a chosen value and TTL
- Expire or delete a stale cache key after you approve it
- Push to or pop from a list to manage a job queue
- Update fields in a hash or members in a sorted set
- Increment a counter and read back the new value
- Inspect a key's type and TTL before changing it
Can Claude set and update keys in Redis?
Yes. A full read-write Redis connector lets Claude set and update keys with chosen values and TTLs, increment counters, and mutate hashes and sorted sets against a live instance. It works through a scoped ACL user, so Claude only touches the keys and commands that user is allowed to reach.
Can Claude manage a job queue in Redis?
Yes. Claude can push to or pop from lists to manage a job queue, update queue entries, and read back state against your instance. The list mutations run as scoped write tools, separated from read tools, so queue work happens through Claude instead of a manual command-line session.
Will Claude delete or flush Redis keys without my approval?
No. Destructive commands like DEL, EXPIRE, and FLUSH are gated write actions. Claude can propose the change and show which keys it affects, but the command runs only after you approve it. Reads and routine sets flow freely while anything that clears data waits for a human.
How a Redis connector works
We build a small MCP server that connects to your Redis instance over a scoped connection, using TLS and an ACL user limited to the keys and commands the work needs. Read tools (GET, lookups, key inspection) and write tools (SET, DEL, list and hash mutations) are separated, and destructive commands like DEL or FLUSH require your confirmation. The connection is locked to allowlisted IPs, and Claude never gets more access than that ACL user already has.
Frequently asked questions
Can Claude write to Redis, not just read keys?
Will Claude delete or flush Redis keys without my approval?
Does the connector get more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.