Skip to content

fix: stabilize Redis MCP server startup in FaaS environments#407

Merged
cuericlee merged 1 commit into
volcengine:mainfrom
Y-Rookie:main
Jun 9, 2026
Merged

fix: stabilize Redis MCP server startup in FaaS environments#407
cuericlee merged 1 commit into
volcengine:mainfrom
Y-Rookie:main

Conversation

@Y-Rookie

@Y-Rookie Y-Rookie commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR fixes Redis MCP server startup issues in FaaS environments.

Changes

  • Pin mcp[cli] to 1.12.4
  • Pin pydantic to >=2.10,<2.11
  • Bind HTTP server to 0.0.0.0 by default
  • Support overriding transport via MCP_SERVER_TRANSPORT
  • Keep default transport as stdio

Why

In FaaS deployments, the Redis MCP server could fail to start because:

  • some runtime environments load an incompatible pydantic version for the current mcp
  • streamable-http mode only listened on 127.0.0.1, causing health check failures

Validation

Verified both modes successfully with real Redis credentials:

  • stdio
  • streamable-http

Both were able to call describe_db_instances successfully.

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.

@cuericlee cuericlee left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@zBaitu

zBaitu commented Jun 9, 2026

Copy link
Copy Markdown

/lgtm

@cuericlee cuericlee merged commit 3275f5c into volcengine:main Jun 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants