fix(codex): stabilize awsknowledge MCP startup with codex-specific compatibility transport#139
Open
faishal882 wants to merge 1 commit intoawslabs:mainfrom
Open
Conversation
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 Codex startup failures for
awsknowledgeMCP by introducing a Codex-specific compatibility transport path.Issue: #130
Problem
Users running Codex could hit MCP startup failure for
awsknowledgewith:Observed behavior from reproduction:
POSTJSON-RPCinitializetohttps://knowledge-mcp.global.api.awsreturns valid MCP init response.GET/stream path behavior can redirect/close, which can break Codex streamable-http startup flow.This caused handshake failure during the
initializednotification phase.What changed
1) Added Codex-specific MCP configs in affected plugins
New files:
plugins/deploy-on-aws/.mcp.codex.jsonplugins/migration-to-aws/.mcp.codex.jsonplugins/databases-on-aws/.mcp.codex.jsonIn these Codex-specific files,
awsknowledgeuses a local stdio proxy transport:{ "type": "stdio", "command": "uvx", "args": ["fastmcp", "run", "https://knowledge-mcp.global.api.aws"], "env": { "FASTMCP_LOG_LEVEL": "ERROR" }, "timeout": 120000 }2) Pointed Codex manifests to Codex-specific MCP configs
Updated:
plugins/deploy-on-aws/.codex-plugin/plugin.jsonplugins/migration-to-aws/.codex-plugin/plugin.jsonplugins/databases-on-aws/.codex-plugin/plugin.jsonChange:
"mcpServers": "./.mcp.json""mcpServers": "./.mcp.codex.json"3) Added Codex troubleshooting and rollback guidance
Updated:
docs/TROUBLESHOOTING.mdAdded:
awsknowledgestartup failure sectionawsknowledgeFails to Start Due to Transport Channel Closure During Handshake #130Why this approach
Validation
Ran full project build requirements via
mise run build:All checks passed.
Notes
.mcp.jsonfiles.