What it does
cacheport stores a string value under a key, optionally with an expiry, reads it back, deletes one or more keys, and lists keys matching a glob pattern. It talks to Redis directly using the RESP wire protocol over a TCP socket, without a bundled client library, and returns the server's own replies. Refused connections and server errors are reported as errors, never as substitute values.
It suits an AI agent or script that needs simple key-value caching in Redis. The MCP server exposes the tools set, get, delete and list over stdio, and the same binary works as a CLI with exit codes 0, 1 and 2. The MCP server starts and lists its tools without a Redis server running; only an actual operation contacts the server.
The Redis target is given as a redis:// or rediss:// URL, with an optional port (default 6379), password and database index, or through the REDIS_URL, CACHEPORT_REDIS_URL, or split REDIS_HOST, REDIS_PORT and REDIS_PASSWORD variables. Without any of these, it connects to localhost:6379. Each operation opens its own connection, running AUTH and SELECT first when a password or non-zero database is set. The project is released under the MIT licence.
Limitations and requirements
Requires a reachable Redis server; connection failures and server errors are returned as tool or command errors. An expiry must be positive: zero or negative values are refused before anything is sent. Fractional expiry seconds are floored.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/cacheport
Key-value cache over Redis: set, get, delete and list keys.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it