All integrations
Redis
Databases
Give agents direct access to keys, hashes, lists and sets — for state that lives in Redis rather than a relational store.
What teams build with this
Read cached or session state while diagnosing an issue
Check queue and counter values during an investigation
Set or expire keys as part of an operational workflow
What this integration is allowed to do
6 read-only
Reads data. Cannot change anything in the connected system.
5 reversible
Writes data, but the change can be undone.
1 irreversible
Writes data in a way that cannot be automatically undone.
Attach only the tools an agent needs. Run the whole integration against a vendor sandbox or the Fruxon simulator before it touches production.
Available tools
Each tool is attached per agent step, so an agent only gets what its job requires.
get | Get a string value by key | Read-only |
set | Set a string value with optional TTL | Reversible |
keys | Scan for keys matching a pattern (SCAN, production-safe) | Read-only |
delete | Delete one or more keys | Irreversible |
expire | Set or check key expiration (TTL) | Reversible |
hash_get_all | Get all fields and values of a hash | Read-only |
hash_set | Set fields in a hash | Reversible |
list_range | Get elements from a list by index range | Read-only |
list_push | Push elements to a list (LPUSH or RPUSH) | Reversible |
set_members | Get all members of a set | Read-only |
set_add | Add members to a set | Reversible |
info | Get server information (memory, clients, keyspace, etc.) | Read-only |
Connect Redis to your agents
Set up credentials once at the tenant level, then attach the tools you need to any agent.
