-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Support streamable http mcp #3027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# Conflicts: # src/core/Cline.ts
# Conflicts: # locales/ca/README.md # locales/de/README.md # locales/es/README.md # locales/fr/README.md # locales/hi/README.md # locales/it/README.md # locales/ja/README.md # locales/ko/README.md # locales/pl/README.md # locales/pt-BR/README.md # locales/tr/README.md # locales/vi/README.md # locales/zh-CN/README.md # locales/zh-TW/README.md # src/core/Cline.ts # src/core/__tests__/Cline.test.ts
# Conflicts: # src/services/mcp/McpHub.ts # src/services/mcp/__tests__/McpHub.test.ts
…s/vars with underscore
|
|
Sorry if this sounds newbie. But are there any pre-existing streaming MCP's servers out there that we can test with other than just making sure things aren't breaking with a purpose written MCP for testing? What form does the stream manifest itself as? Periodic updates to the chat? Smooth response flowing into the chat detail without "jumps" and hiccups? Thanks! |
This update mainly supports the transmission protocol part, from the previous SSE to the current Streamable HTTP. Its main advantages are to simplify the deployment complexity, support flexible communication modes (one-time response or streaming push), and optimize network stability.
As for the demonstration of the streaming transmission mentioned, since the previous SSE also supported it, I think it will be very useful for large data volumes or audio data streams. We can specifically test this aspect. |
|
Hi all, Good to know: I saw the vs code itself is now supporting the streamable mcp servers |
|
Hey @aheizi, |
- Add missing client.connect() call in connectToServer method - Implement connection-level fallback from StreamableHTTP to SSE - Replace console.log with structured logging using appendErrorMessage - Prioritize modern StreamableHTTP transport over legacy SSE - Add proper error handling and connection state validation - Only mark connections as 'connected' after successful handshake Addresses all code review points from Daniel in PR RooCodeInc#4406: 1. Missing connection-level fallback for StreamableHTTP 2. Improper logging using console.log 3. Incorrect client.connect() handling Technical improvements: - Robust transport fallback mechanism - Production-ready connection establishment - Foundation for completing StreamableHTTP implementation (PR RooCodeInc#3027) - Better compatibility with modern MCP servers Related to RooCodeInc#4189: Improves StreamableHTTP reliability though full mcp-go SSE compatibility requires SDK update to v1.12.1+ for protocol fixes.
Context
Support streamable http mcp
Based on:#2685
Implementation
Screenshots
How to Test
Get in Touch