feat: add streamable HTTP transport support #18
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
The MCP server currently only supports stdio transport, which limits deployment options. I'm adding HTTP transport support so we can run the server as a standalone HTTP service, enabling use cases like: - Remote access without needing a local process - Containerized deployments - Multiple clients sharing a single server instance The implementation uses Express with the MCP SDK's StreamableHTTPServerTransport. Sessions are tracked via the MCP-Session-ID header, allowing stateful interactions across requests. Configuration can be done via CLI flags (--streamable-http, --port=, --host=) or environment variables (FRED_MCP_TRANSPORT, PORT, HOST). The server defaults to stdio for backwards compatibility. I've also added a /health endpoint for monitoring active sessions. Bumping to 1.1.0 since this is a new feature with no breaking changes.
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.
The MCP server currently only supports stdio transport, which limits deployment options. I'm adding HTTP transport support so we can run the server as a standalone HTTP service.
This enables use cases like:
The implementation uses Express with the MCP SDK's StreamableHTTPServerTransport. Sessions are tracked via the MCP-Session-ID header, allowing stateful interactions across requests.
Configuration can be done via CLI flags (
--streamable-http,--port=,--host=) or environment variables (FRED_MCP_TRANSPORT,PORT,HOST). The server defaults to stdio for backwards compatibility.I've also added a
/healthendpoint for monitoring active sessions.Bumping to 1.1.0 since this is a new feature with no breaking changes.