* fix(use-mcp): connect to mcp fails with handleMessage function
* Upping the SDK version cooks every test
* checking out neighbouring SDK
* Getting more random port collisions locally :/
I will fix this properly... eventually.
* Running `wrangler types` on example servers
* Updated to SDK v1.13.2
* prettier
---------
Co-authored-by: ksankaran <kv.coder@gmail.com>
Co-authored-by: Glen Maddern <glen@glenmaddern.com>
* /sse still not working
* Add transport type selector to inspector UI and comprehensive transport testing
- Add transport type dropdown to inspector UI (auto, HTTP, SSE) with session storage persistence
- Update test framework to support transport type selection in test scenarios
- Add comprehensive test cases covering:
* Working /mcp endpoints with auto and HTTP transports
* SSE endpoint with SSE transport (expected to pass)
* SSE endpoint with auto transport (expected to fail - demonstrates current fallback issue)
- Test structure now provides clear visibility into transport-specific behavior
- All tests properly named and categorized for easy identification of failing scenarios
* Gearing up to "make amp do it"
* fix: improve SSE fallback logic in auto transport mode
- Fix issue where SSE fallback was not attempted when HTTP transport failed
- Specific error types (404, 405, CORS) now correctly trigger SSE fallback
- Allow SSE fallback even when component state is 'failed' from previous attempts
- Maintain proper error handling for non-fallback HTTP errors
- All 6 transport scenarios now pass integration tests
The core issue was that failConnection() was being called for HTTP errors
before returning 'fallback', which set the component state to 'failed' and
prevented the orchestration logic from attempting SSE fallback. Now only
specific HTTP errors that should trigger fallback avoid calling failConnection
immediately, allowing the SSE transport to be attempted as expected.
---------
Co-authored-by: Glen Maddern <glen@glenmaddern.com>
