redis-mcp-server
Redis MCP server exposing Redis management/control tools via an MCP interface implemented as SSE (Spring Boot + spring-ai MCP webmvc starter). Supports basic key operations: set/get/delete and pattern-based key listing (with optional expiration for set).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README does not mention authentication/authorization, TLS requirements, or rate limiting headers/behavior. Using SSE over HTTP in local examples suggests TLS/auth must be handled by deployment configuration. Dependency hygiene cannot be validated from the provided data; Spring Boot dependencies may include security fixes but no CVE/status information is available here.
⚡ Reliability
Best When
You run a trusted MCP client (e.g., Cursor) in a controlled environment and need a simple tool-based interface for basic Redis key operations.
Avoid When
You need robust authentication/authorization, auditability, and strict production-grade safety controls that are not described in the README.
Use Cases
- • Let an AI agent read/write Redis keys safely through a constrained tool interface
- • Automate cache inspection and key management (e.g., list by pattern, delete keys)
- • Provide a local/devops control plane for Redis during development using Cursor MCP tool integration
Not For
- • High-throughput production workloads without careful rate limiting and access controls
- • Storing sensitive data without strong network/auth controls around the MCP endpoint
- • Operations requiring full Redis administrative capabilities beyond basic key operations
Interface
Authentication
No authentication/authorization mechanism is described in the provided README. Access control likely depends on surrounding deployment (e.g., network policies, reverse proxy) rather than app-level auth.
Pricing
Agent Metadata
Known Gotchas
- ⚠ Pattern-based key listing can be expensive if patterns match many keys; without documented paging/limits, agents may request overly broad lists.
- ⚠ No documented auth/rate limiting/error contract: agents may repeatedly call tools on failures or in loops, so external safeguards may be needed.
- ⚠ Delete supports 'one or multiple keys' but exact semantics (bulk delete limits, behavior on missing keys) are not described.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for redis-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.