Feat: Add HTTP Streamable Server Transport Support #63
Conversation
src/index.ts
Outdated
|
|
||
| const transports: { [sessionId: string]: StreamableHTTPServerTransport } = {}; | ||
|
|
||
| // 单一端点处理所有MCP请求 |
There was a problem hiding this comment.
I am not a reviewer. Nor am I affiliated.
But I could use clarification on what this comment means.
There was a problem hiding this comment.
Based on google translate: // Single endpoint handles all MCP requests
There was a problem hiding this comment.
Thank you for pointing this out and for your interest in the code! The comment means that all MCP (Multi-Channel Protocol) requests are handled through a single API endpoint. I appreciate your feedback, and I will update the comment to English to make it clearer for everyone.
|
Hello! Will this PR eventually be merged? We are currently waiting on a reliable streamable http implementation. Thanks! @nickscamara @tomkosm |
|
Hey @tradeqvest, yes of course, sorry about the delay! We are working on pushing improvements to our mcp earlier next month but in the meantime we should totally merge this! @tomkosm can you review it today if possible? Thanks! |
|
Thank you for the quick reply! Looking forward to it. |
|
Added in 6817c87 |
7 participants
Body:
Hi team,
This PR introduces support for HTTP Streamable transport to the Firecrawl MCP server. This enhancement provides an alternative way for clients to connect and interact with the server, aligning with the latest specifications and offering more flexibility for integrations.
Key Changes:
runHTTPStreamableServer()function insrc/index.tsto enable the HTTP Streamable server.README.mdto include:HTTP_STREAMABLE_SERVERand configuration examples.This addition is in the spirit of open source and aims to enhance the capabilities and interoperability of the Firecrawl MCP server. We believe this will be a valuable addition for users looking for different transport options.
For more information on the Model Context Protocol and its specifications, please refer to the official documentation: https://modelcontextprotocol.io/specification/2025-03-26
We hope this contribution is a welcome addition to the project and look forward to your feedback!
Best regards,
Dangoron