REDIS

This Redis MCP Server provides a set of standardized tools that let large language models interact with Redis key-value stores. The available tools include set (to store a key-value pair with an optional expiration), get (to retrieve a value by key), delete (to remove one or more keys), and list (to enumerate keys matching a pattern). You can run the server via npx or by invoking the package directly if installed globally, and then connect to a Redis instance using a Redis URL such as redis://localhost:6379. Once running, you can issue MCP calls to perform common Redis operations in a structured way, enabling LLMs to manage Redis data without executing raw Redis commands directly. The server is designed to work with Claude Desktop or other MCP-enabled clients by configuring the mcpServers section in their configuration to point to the npx invocation (or an equivalent Node-based startup).

Prerequisites:

• Node.js and npm installed on the host
• Access to a Redis server (local or remote) with a reachable URL

Installation and setup:

1. Install the MCP server package via NPX (no permanent installation required):

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

2. Optional: install globally for easier reuse:

npm install -g @gongrzhe/server-redis-mcp@1.0.0

3. Start the server (if installed globally, you can run the package name with a Redis URL):

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

4. Verify connectivity by issuing a test command to connect to your Redis instance through the MCP interface. Ensure your Redis server is reachable from the host where you run the MCP server.

If you prefer using a local build path, you can build the project and run the built index with Node, as described in the repository's development guidance.

Notes and tips:

• The server targets a Redis-compatible endpoint; ensure the Redis URL is correct and that any required authentication (password) is included in the URL if needed (e.g., redis://:password@host:port).
• The available tools map to common Redis operations: set (with optional expiration), get, delete, and list (pattern-based key scanning). Use descriptive keys and manage expiration as needed.
• If you plan to run in Docker or behind a firewall, ensure the container or host can reach the Redis endpoint.
• You can configure the client (Claude Desktop or other MCP clients) to point to the npx invocation as shown in the README, or run the server via a Node command if the package is installed locally.
• When using docker or specialized environments, consider providing the Redis URL as the first argument to the MCP launcher to simplify configuration.