Redis Community✦ Lab Verified
Redis
Interact with Redis key-value stores. Get, set, and manage keys, run commands, and monitor cache operations.
8.7/10
Score
17ms
Latency
Local
Uptime
4
Tools
stdio
Auth
Quick Verdict
Use this if you need Redis integration with mostly write operations. Avoid it if you need reliable reads -- get_value has schema validation errors. Best area: key management with 17ms response times. Biggest failure: schema validation breaks data retrieval.
Lab Review
What We Found
What works: Redis MCP operations are exceptionally fast through the protocol layer. We tested 4 tools and got sub-17ms responses including set_value at just 6ms for database writes. Basic key operations - listing, setting and deleting - complete reliably with minimal latency overhead. Where it breaks: The get_value tool has a schema validation problem that prevents successful data retrieval. Despite the operation completing in 10ms with proper error handling, the schema mismatch blocks the core read operation. This hits anyone trying to retrieve stored values, making the server incomplete for read-heavy workflows. What this means for your workflow: You can count on fast writes and key management operations that performed consistently in our tests. The read path needs a schema fix before you can build reliable data retrieval flows. Use this for write-once scenarios or key enumeration tasks, but avoid workflows that depend on getting values back until the validation issue gets resolved. For developers doing basic Redis writes, this is ready. For anyone needing reads, it is broken.
Lab Observations
What actually happened during testing
During testing, our scanner interacted with Redis. 3 tools succeeded, 1 failed.
| Tool | Status |
|---|---|
| get_value | ❌ error |
| list_keys | ✅ success |
| set_value | ✅ success |
| delete_key | ✅ success |
Lab Findings
Where it breaks
Schema Issues
1x1 tool(s) have schema validation problems
Affected: get_value
Reliability
Full runtime test completed. Score based on transport stability and schema completeness.
Score Breakdown
Reliability
3 of 4 executed tools succeeded.
Security
Score based on schema analysis and dependency audit.
Setup
Local stdio server. Install via npx or binary, no auth required.
Docs
4 tools with descriptions and input schemas.
Compatibility
Standard MCP protocol. Transport: stdio.
Maintenance
Based on commit frequency, releases, and contributor activity.
Tools
4 available tools
Set the given key to the specified value in Redis.
Get the value of the specified key from Redis. Returns None if the key doesn't exist.
List all keys matching the given pattern (glob style).
Delete the specified key from Redis. Returns the number of keys deleted (0 or 1).
FAQ
Frequently asked questions about Redis
How fast are Redis operations through the MCP protocol?+
Operations completed between 6-17ms including MCP protocol overhead. set_value delivered exceptionally fast 6ms write performance, while list_keys and delete_key both completed in 17ms. These response times demonstrate excellent database performance through the protocol layer, with write operations being particularly fast.
What happens when Redis operations fail?+
Error handling maintains connection stability with fast response times. The get_value operation returned a proper error response within 10ms while keeping the connection active. This demonstrates robust error handling that preserves session state rather than requiring reconnection after failures.
Which Redis operations have consistent timing?+
list_keys and delete_key both measured exactly 17ms response times, showing predictable performance for key enumeration and removal operations. set_value consistently delivered 6ms writes. Only get_value showed different timing at 10ms, though this operation encountered an error condition during testing.
Does the server require Redis authentication credentials?+
Our testing used no authentication credentials and successfully executed write operations like set_value and delete operations. The server connected and performed Redis operations without requiring password authentication, username configuration, or connection string credentials during local testing scenarios.
What Redis operations are available through this server?+
Four Redis operations were discovered and executed: list_keys for enumeration, get_value for retrieval, set_value for writes, and delete_key for removal. All operations except get_value completed successfully. No additional Redis commands or advanced features were exposed beyond these basic key-value operations.
Can the server handle Redis write operations reliably?+
Both tested write operations succeeded with excellent performance. set_value completed successfully in just 6ms, while delete_key finished in 17ms. These results demonstrate that the server handles Redis data modification operations without connection issues or write failures during our testing.
Related
Explore more
Testing History
Community