feat: add Valkey power for Redis/Valkey integration #41
+289
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds Valkey power to enable direct interaction with Valkey/Redis instances from Kiro. Developers can execute commands, manage data structures, and administer servers without leaving the IDE.
Motivation
Valkey/Redis is widely used for caching, session management, message queuing, and real-time data processing. Having direct access to Valkey instances from Kiro streamlines development workflows by eliminating context switching between the IDE and separate Redis CLI tools. This is particularly useful for:
The power supports various deployment scenarios including local development, remote instances with authentication, SSL/TLS connections, and cluster mode - making it suitable for both development and production troubleshooting.
Verifications
valkey/POWER.mdwith comprehensive documentationvalkey/mcp.jsonwith default configurationREADME.mdwith Valkey entry