
by YawLabs
An MCP server from Yaw Labs for exploring and diagnosing Redis and Valkey instances from an MCP client. It is read-only by default and always enumerates keys with SCAN.
PluginContact for pricing
Step 1: Create a .mcp.json in your project root that runs npx with @yawlabs/redis-mcp.
Step 2: Set the REDIS_URL environment variable to your connection string; the server exits at startup if it is missing.
Step 3: Restart your MCP client and approve the redis server when prompted.
Step 4: Ask the agent to scan keys, check a key's TTL and memory, or run the health and advisor tools.
Step 5: Add ALLOW_WRITES=1 only on dev or test instances if you want mutating commands.
The README says so for read use: key enumeration uses SCAN with a cap, and mutating commands are blocked unless ALLOW_WRITES=1 is set.
It works against Redis 6 and later and against Valkey. Some health fields may come back as null if the server does not expose them.
No. EVAL, FUNCTION, SCRIPT, MULTI and MONITOR are never exposed, even with writes on.
Node 20 or later and a REDIS_URL environment variable.
Requirements
CtxLint MCPctxlint checks AI agent context files and MCP server configs against your real codebase and flags drift before your agent acts on it. It runs as a CLI, CI step, pre-commit hook or MCP server.
YawLabs AWS MCP@yawlabs/aws-mcp is a small MCP server that calls AWS through your local aws CLI, with built-in SSO re-login, generic resource CRUD and live docs lookup. It is presented as an alternative to AWS's own MCP server.
Caddy MCPAn MCP server from Yaw Labs for managing Caddy web servers through Caddy's admin API. It provides 18 tools and 4 resources for config, routes, reverse proxies, TLS, PKI and metrics.
CRAPKit MCPcrapkit scores every function in a repository by complexity times uncovered risk, ranks the worst, and blocks commits that add more. An optional MCP server lets coding agents use its JSON output.