fix: stabilize Redis MCP server startup in FaaS environments#407
Merged
Conversation
Pin the Redis MCP server to a FastMCP and pydantic combination that works in ByteFaaS, and bind the HTTP server to 0.0.0.0 so streamable-http deployments can pass health checks while keeping stdio as the explicit default transport.
|
/lgtm |
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.
Summary
This PR fixes Redis MCP server startup issues in FaaS environments.
Changes
mcp[cli]to1.12.4pydanticto>=2.10,<2.110.0.0.0by defaultMCP_SERVER_TRANSPORTstdioWhy
In FaaS deployments, the Redis MCP server could fail to start because:
pydanticversion for the currentmcpstreamable-httpmode only listened on127.0.0.1, causing health check failuresValidation
Verified both modes successfully with real Redis credentials:
stdiostreamable-httpBoth were able to call
describe_db_instancessuccessfully.