Sky AI delivery robots: Zipline

apparently already in USA, and much more in Africa

What is Amazon doing?

Zipline Drone Delivery & Logistics

Zipline - YouTube

Keller Rinaudo Cliffton (@Keller) / X

Science Corner Special! David Friedberg, Cleo Abram, Alex Filippenko, and Keller Rinaudo Cliffton - YouTube

AI MCP protocols: SSE vs Streamable HTTP

Note: SSE Transport is deprecated as of MCP specification version 2025-03-26, replaced by Streamable HTTP.

• Transport: Uses HTTP/1.1 with Server-Sent Events for server-to-client messages and HTTP POST for client-to-server messages MCP FrameworkModelcontextprotocol
• Not WebSockets: MCP SSE uses standard HTTP with Server-Sent Events, not WebSockets or gRPC Transports – Model Context Protocol Specification
• Not HTTP/2 or HTTP/3: Uses standard HTTP/1.1

Why It's Being Replaced

SSE transport has three major limitations:

1. No support for resumable streams
2. Requires server to maintain long-lived, highly available connections
3. Only allows server messages to be delivered via SSE (unidirectional)

Servers typically expose multiple endpoints:

• /sse + /messages (legacy SSE)
• /mcp (new Streamable HTTP)

Transport Overview | MCP Framework

• STDIO Transport | MCP Framework
• SSE Transport | MCP Framework
• HTTP Stream Transport | MCP Framework

Transports - Model Context Protocol

SSE vs Streamable HTTP: Why MCP Switched Transport Protocols

MCP (Modal Context Protocol), one of the most popular and widely used AI protocols today, replaced the HTTP+SSE transport mechanism with Streamable HTTP starting from protocol version 2025-03-26. That has marked a significant change in the protocol’s architecture.

Specifically, MCP uses JSON-RPC 2.0 as its wire format between clients and servers. For transmission of JSON-RPC messages, it relies on standard transport mechanisms like HTTP+SSE or Streamable HTTP (among stdio — for communication over standard in and standard out on local servers).


Those specialized transport layers are necessary because traditional HTTP’s request-response model is inefficient for real-time AI communication. That is because plain HTTP introduces high overhead and latency due to frequent connection setups. In contrast, MCP requires continuous, low-latency data streams—something HTTP+SSE and Streamable HTTP are designed to handle.

GitHub - sidharthrajaram/mcp-sse: A working pattern for SSE-based MCP clients and servers

Course: The Complete Model Context Protocol (MCP) Masterclass | Udemy Business

GitHub - pdichone/mcp-course-code

GitHub - pdichone/mcp-recipe-final