Redis Mcp
Let your coding agent inspect Redis keyspaces, TTLs, memory, and slowlogs without writing ad-hoc redis-cli one-liners.
Overview
redis-mcp is a MCP server for the Operate phase that gives AI assistants read-first Redis key exploration, stats, and DBA-style advisory without defaulting to destructive writes.
What is this MCP server?
- Read-first design: explore keys via SCAN instead of risky full-key dumps
- Keyspace, TTL, memory, and slowlog stats in one MCP surface
- DBA-style advisor tooling aimed at solo builders running Redis in prod
- stdio npm package @yawlabs/redis-mcp (v0.1.2) for Claude Code–style agents
- Fits cache/session debugging without granting write-heavy Redis admin by default
- npm package @yawlabs/redis-mcp at server version 0.1.2
- Transport: stdio per MCP server schema 2025-12-11
What problem does it solve?
When Redis misbehaves in production, solo builders waste time bouncing between agents, CLI, and dashboards just to see keys, TTLs, and slow commands safely.
Who is it for?
Indie SaaS or API builders who operate their own Redis (or managed Redis) and want agent-driven diagnostics during incidents or cache tuning.
Skip if: Teams that need a full Redis admin GUI, bulk data mutation, or a replacement for infrastructure-as-code provisioning of Redis clusters.
What do I get? / Deliverables
After you register redis-mcp, your agent can answer Redis health and keyspace questions from the same session where you debug application code.
- SCAN-based key exploration reports inside agent chats
- Aggregated keyspace, TTL, memory, and slowlog context for triage
- Advisor-style notes the agent can use in postmortems or tuning tasks
Recommended MCP Servers
Journey fit
Redis health and key discovery matter after you ship caches, queues, and sessions—not during initial ideation. Slowlog, memory, and SCAN-based exploration are day-two observability tasks that sit in production monitoring.
How it compares
MCP database inspector for Redis, not a Redis hosting product or ORM integration skill.
Common Questions / FAQ
Who is redis-mcp for?
Solo and small-team builders who run Redis-backed apps and want their AI coding agent to inspect keys, TTLs, memory, and slowlogs read-first.
When should I use redis-mcp?
Use it during Operate when debugging cache leaks, mystery keys, TTL issues, or slowlog spikes after you have a reachable Redis instance and credentials.
How do I add redis-mcp to my agent?
Install @yawlabs/redis-mcp from npm, configure stdio MCP in Claude Code, Cursor, or a compatible host, and point it at your Redis URL with least-privilege access.