# redis/mcp-redis [Verified] [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/redis/mcp-redis  
**GitHub Stars:** 620  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/redis-mcp-redis

## Description
The Redis official MCP Server offers an interface to manage and search data in Redis.

## Tools
Capabilities this server exposes over MCP:

- **string**
- **hash**
- **list**
- **set**
- **streams**
- **JSON**
- **docs**
- **MCP_DOCS_SEARCH_URL**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-redis": {
    "command": "uvx",
    "args": ["--from"]
  }
}
```

## Documentation

## What redis/mcp-redis MCP server does

The redis/mcp-redis MCP server lets an MCP client interact with Redis through agent-facing tools. It supports common Redis structures and operations rather than limiting access to a single data model. Agents can work with strings, hashes, lists, sets, sorted sets, streams, and JSON documents. Hashes can also hold vector embeddings.

The server supports use cases such as caching values, storing session data with expiration, representing objects with field-value pairs, maintaining queues, tracking unique members, and building score-ordered collections. Stream tools cover adding and reading entries, managing consumer groups, deleting entries, and acknowledging processed messages. Pub/sub tools support publishing, stateful channel or pattern subscriptions, and reading queued messages through subscription handles.

Additional capabilities include tools for managing vector indexes and running vector searches, a server-management tool that returns database information, and a documentation search tool. The documentation search uses the `MCP_DOCS_SEARCH_URL` HTTP API and can retrieve Redis documentation, tutorials, and best practices.

## How it works

The redis/mcp-redis MCP server uses the stdio transport. An MCP-compatible client starts the process and sends tool requests over standard input and output. The process connects to the target Redis database using a connection URI. The URI identifies the Redis host and port and can include a username, password, logical database number, and connection options.

Use `redis://` for a standard connection or `rediss://` for an encrypted connection. TLS settings can be supplied as URI options, including certificate verification behavior and a CA certificate path. The logical database is expressed in the URI path, such as `/0`.

## Setup and configuration

The redis/mcp-redis MCP server is distributed as the `redis-mcp-server` PyPI package and can be run with `uvx`. A local Redis configuration uses:

```json
{
  "command": "uvx",
  "args": [
    "--from",
    "redis-mcp-server@latest",
    "redis-mcp-server",
    "--url",
    "redis://localhost:6379/0"
  ]
}
```

The package can also be installed with `pip`, then started with the `redis-mcp-server` command and a `--url` argument. GitHub-based execution is supported with `uvx`; tagged releases are recommended because the main branch is under active development and may include breaking changes.

Redis credentials can be included in the URI, for example through the `user:secret@host` portion. Azure Managed Redis can use EntraID authentication. The documented runtime requires Python 3.14 or newer.

## Limitations and notes

Only stdio transport is documented as supported in the provided material. Streamable HTTP support is described as planned for the future. A reachable Redis deployment is required for data operations, and encrypted connections may require appropriate certificate settings. The documentation-search feature depends on the `MCP_DOCS_SEARCH_URL` HTTP API.

_Full upstream README: https://allmcps.com/mcp/redis-mcp-redis/readme_