Add missing capabilities and improve connection handling for server-redis#1166
Merged
Add missing capabilities and improve connection handling for server-redis#1166
Conversation
tadasant
approved these changes
Apr 3, 2025
Member
tadasant
left a comment
There was a problem hiding this comment.
Nice! Thanks for digging into this!
PazerOP
referenced
this pull request
in PazerOP/mcp-template
Jul 15, 2025
…nd-memory Add missing capabilities and improve connection handling for server-redis
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR adds the missing
toolscapability and improves connection and error handling for the reference Redis MCP server.Server Details
Motivation and Context
Was not able to start or use server-redis tools. After adding missing capabilities, if there was no redis host running then Claude Desktop got spammed with error logs.
How Has This Been Tested?
Tested with Claude Desktop on Windows with Memurai, screenshots below:
Breaking Changes
None
Types of changes
Checklist
Additional context
This should also solve this issue since the typescript changes should trigger a new tag and npm version to get published: #856