[codex] Support Streamable HTTP MCP aliases#952
Merged
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
streamableHttp,streamable-http,streamable_http) to Proma's canonicalhttptransportmcp.json, validating server configs, and building Agent SDK MCP server confighttptypeWhy
Proma already labels
httpas Streamable HTTP in the UI and passestype: 'http'to the Claude Agent SDK, which is the SDK's current Streamable HTTP discriminant. However, external MCP examples commonly usetype: 'streamableHttp', and our own Nowledge prompt used that spelling. Those configs could fail validation or be skipped at runtime because Proma only acceptedhttpandssefor URL-based MCP servers.Validation
bun test packages/shared/src/utils/mcp-transport.test.tsbun run --filter='@proma/shared' typecheckbun run --cwd apps/electron typecheckgit diff --check