Connect LLMs to Redis Data

A Redis MCP server exposing four tools for key-value operations: set stores a key-value pair with an optional expireSeconds expiration, get retrieves a value by key, delete removes one or more keys accepting either a single key or an array of keys, and list enumerates Redis keys matching a glob pattern, defaulting to *. It lets an LLM read, write, expire, and enumerate Redis keys directly through standardized MCP tools. The project's README notes that a separate redis-plus branch expands this to 62 Redis MCP tools, though this v1.0.0 package ships only the four listed above.

Use it when an LLM needs direct key-value access to a Redis instance - setting, reading, deleting, or listing keys by pattern. It is not intended for advanced Redis data structures such as lists, sets, hashes, streams, or pub/sub - those would require the expanded redis-plus branch rather than this v1.0.0 package.

Input types are minimal and explicit: set takes key (string), value (string), and an optional expireSeconds (number); get takes only key (string); delete takes key as either a single string or a string array, so a single call can remove one key or many; list takes an optional pattern (string) defaulting to *. No tool accepts a numeric index, offset, or field name - Redis's richer per-type commands are entirely out of scope for this package.

npx @gongrzhe/server-redis-mcp@1.0.0 redis://localhost:6379

Or install via Smithery with npx -y @smithery/cli install @gongrzhe/server-redis-mcp --client claude, install it globally with npm, or build from source by cloning the repository, running npm install, and then npm run build. A Claude Desktop config looks like:

{
  "mcpServers": {
    "redis": {
      "command": "npx",
      "args": ["@gongrzhe/server-redis-mcp@1.0.0", "redis://localhost:6379"]
    }
  }
}

Docker is also supported - build with docker build -t mcp/redis ., then run the image with the Redis connection URL as an argument; on macOS, use host.docker.internal in place of localhost if Redis is running on the host network. The server can equally be launched with node directly against a built index.js path instead of through npx, which is useful when a specific local build needs to be pinned in the client configuration rather than resolved dynamically.

Developers who want an LLM to read and write Redis key-value data directly - caching lookups, session data, or simple key-value storage - without building a custom Redis client integration themselves. It's also a reasonable starting point for teams who want to run their own alternative to the official Redis Docker image (mcp/redis), since it can also be installed globally via npm and invoked as @gongrzhe/server-redis-mcp with the target Redis URL as its only argument. Licensed under the ISC License.