Operate common Redis structures
Tools cover strings, hashes, lists, sets and sorted sets for sessions, queues, tags and leaderboards.
Documentation ↗MCP server / databases / source-linked
Redis MCP suits fast operational data: keys, hashes, lists, sets, streams, sorted sets and vector search. The incremental value is structure-aware operations from an agent, but the current official server does not promise Streamable HTTP, so deployment is local or bridged.
Identify the implementation and the job it supports.
Redis MCP suits fast operational data: keys, hashes, lists, sets, streams, sorted sets and vector search. The incremental value is structure-aware operations from an agent, but the current official server does not promise Streamable HTTP, so deployment is local or bridged.
The documented interface, authentication and installation path.
Run with a Redis URL through uvx, ideally pinned to a tagged release. Example: `uvx --from redis-mcp-server@latest redis-mcp-server --url redis://localhost:6379/0`. Configure a least-privileged Redis ACL user.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
{"mcpServers":{"RedisMCPServer":{"command":"uvx","args":["--from","redis-mcp-server@latest","redis-mcp-server","--url","redis://localhost:6379/0"]}}}Concrete capabilities with maintainer sources.
Tools cover strings, hashes, lists, sets and sorted sets for sessions, queues, tags and leaderboards.
Documentation ↗The README highlights conversation streams, expiration, indexing and vector search workflows.
Documentation ↗Redis ACL can create a read-only user with `+@read -@write` before the MCP server connects.
Documentation ↗What was checked and what was not tested.
Public maintainer documentation and repositories. This is not a hands-on product review.
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
A bounded evaluation you can reproduce in your own environment.
Suggested evaluation, not an observed test result.
What to inspect: A bounded cache report with no mutation. No Redis connection or performance test was run.
Workflow reference ↗Read these constraints before granting access.
The official README says stdio is supported and Streamable HTTP is planned for the future; do not label it as a remote HTTP service today.
Boundary reference ↗Editorial inference: a natural-language write tool is only as safe as Redis ACLs and key patterns; isolate the database and restrict commands.
Boundary reference ↗Make the expected output explicit before you connect.
A bounded cache report with no mutation. No Redis connection or performance test was run.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| MongoDB MCP | Editorial choice: documents, collections and Atlas governance matter more than key/value speed. | Heavier database model and credential setup. Documentation ↗ |
| PostgreSQL MCP | Editorial choice: analytics depends on SQL schemas and joins. | Archived read-only reference rather than a Redis-like operational store. Documentation ↗ |
Answers specific to this implementation.
The current README documents stdio and says Streamable HTTP support will be added in the future.
Documentation ↗
Create a Redis ACL user with only the required categories and key patterns; avoid embedding broad credentials in arguments.
Documentation ↗
Maintainer documentation used in this record.