Skip to content
Menu

MCP server / databases / source-linked

Redis MCP

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.

Before you choose.

Identify the implementation and the job it supports.

Which implementation is this?
Redis's official MCP Server is a natural-language interface for Redis data and search, currently documented around stdio transport.
Implementation source ↗

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.

Setup and connection.

The documented interface, authentication and installation path.

Connection / transport
stdio
Authentication
Redis URL, ACL credentials or Entra ID for Azure Managed Redis

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"]}}}

What it actually exposes.

Concrete capabilities with maintainer sources.

Documented capability / 01

Operate common Redis structures

Tools cover strings, hashes, lists, sets and sorted sets for sessions, queues, tags and leaderboards.

Documentation ↗
Documented capability / 02

Work with streams and vectors

The README highlights conversation streams, expiration, indexing and vector search workflows.

Documentation ↗
Documented capability / 03

Apply ACL boundaries

Redis ACL can create a read-only user with `+@read -@write` before the MCP server connects.

Documentation ↗

Evidence and method.

What was checked and what was not tested.

WHO

Editorial record

Compiled by clawbot.ai.

HOW

Source method

Public maintainer documentation and repositories. This is not a hands-on product review.

WHEN

Last checked 2026-10-01

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.

Try a specific task.

A bounded evaluation you can reproduce in your own environment.

Proposed workflow: inspect a session cache

Suggested evaluation, not an observed test result.

  1. Connect a read-only ACL user to a non-production database or key namespace.
  2. Ask the agent to summarize key types, TTLs and recent stream entries.
  3. Review any proposed cache writes or deletes before switching to a write-capable user.

What to inspect: A bounded cache report with no mutation. No Redis connection or performance test was run.

Workflow reference ↗

Permissions and limitations.

Read these constraints before granting access.

Boundary / 01

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 ↗
Boundary / 02

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 ↗

Decide by workflow.

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.

Compare the alternatives.

Specific reasons to choose another route, with the tradeoff shown.

Editorial decision guidance inferred from the linked documentation; no quality or speed benchmark.
AlternativeChoose it whenTradeoff
MongoDB MCPEditorial choice: documents, collections and Atlas governance matter more than key/value speed.Heavier database model and credential setup.
Documentation ↗
PostgreSQL MCPEditorial choice: analytics depends on SQL schemas and joins.Archived read-only reference rather than a Redis-like operational store.
Documentation ↗

Questions before setup.

Answers specific to this implementation.

Can I connect this official server over HTTP?

The current README documents stdio and says Streamable HTTP support will be added in the future.
Documentation ↗

How should I limit access?

Create a Redis ACL user with only the required categories and key patterns; avoid embedding broad credentials in arguments.
Documentation ↗