Add HTTP Streamable Transport support #5
Closed
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
- Add HTTP transport implementation in src/httpServer.ts - Update package.json with HTTP transport scripts and dependencies - Enhance src/index.ts to support both STDIO and HTTP modes - Add comprehensive MIGRATION.md documentation - Maintain backwards compatibility with STDIO transport - Support MCP protocol version 2025-03-26 specification
2 tasks
Author
Contributor
|
@MAVRICK-1 thank you for your contribution. Someone else was first with a complete solution already and was awarded the bounty: #3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
HTTP Streamable Transport Migration
Summary
This PR implements HTTP Streamable Transport support for the Supadata MCP server, addressing the GitHub issue #2 and Smithery's STDIO transport deprecation by September 7, 2025.
Changes
src/httpServer.tswith full MCP 2025-03-26 protocol supportMCP_TRANSPORT_MODEenvironment variablestart:httpanddev:httpcommands in package.jsonTesting
HTTP Transport
SUPADATA_API_KEY=your_key npm run start:http # Server runs on port 3000 with endpoints /mcp and /healthSTDIO Transport (Legacy)
SUPADATA_API_KEY=your_key npm run start:stdio # Compatible with existing Claude Desktop/MCP integrationsScreencast.from.2025-08-28.15-44-19.mp4
Migration Benefits
Deployment
The HTTP transport is ready for production deployment on any cloud platform (AWS, Google Cloud, Azure, Heroku, etc.) while maintaining full compatibility with existing STDIO-based integrations.
Fixes #2
/claim #2