
Cloudflare Unveils Next-Generation MCP with Stateless Core
Cloudflare announced the next generation of the Model Context Protocol (MCP), featuring a rewritten, stateless core that runs on Workers. The update includes protocol upgrades, a new feature lifecycle, and an SDK migration path. Early adopters are already running it in production.
Sources and evidence
Summary last validated Aug 29, 2026
Reader actions
Report an issue
Use this for an incorrect summary, wrong source, duplicate story, or wrong category. Submissions are private and do not change the story automatically.
Related coverage
- models
Cloudflare adds Clef-omni multimodal model, speeds Clef and cuts Clef-flash pricing
Cloudflare expanded its Clef decision model family with Clef-omni, which natively processes audio, video, images, and text in a single pipeline. The company also increased Clef inference speeds by up to 2.0x and lowered pricing for Clef-flash.
- infrastructure
Ai2 replaces priority GPU scheduler with budget-based fair-share system
Ai2's AI Infrastructure team replaced its priority-based GPU scheduler with a system using GPU time budgets, hierarchical fair-share allocation, and time-slicing contracts. The institute manages thousands of NVIDIA H100, B200, and B300 GPUs across 88- to 1024-GPU clusters for about 150 researchers, with demand running 2-3x available capacity. The change moved GPU allocation debates into a transparent administrative budgeting process.
- infrastructure
Ai2 details GPU scheduler using time budgets and fair-share allocation
Ai2 published a blog post explaining its new GPU scheduler for its clusters. The scheduler combines time budgets, fair-share allocation, and time-slicing to prioritize high-impact research, shorten queue waits, and keep GPUs busy.
- infrastructure
PyTorch details session-aware agentic inference with NVIDIA Dynamo
PyTorch published a blog post describing session-aware agentic inference with NVIDIA Dynamo. It explains that agentic workloads differ from single-turn chat: an agent session can include a large initial prefill, repeated model calls, and parallel subagents, changing the traffic an inference server handles.
- infrastructure
AWS details multi-team GPU sharing on SageMaker HyperPod
AWS published a reference architecture for sharing one Amazon SageMaker HyperPod EKS cluster across multiple teams. It uses AWS IAM Identity Center for authentication, per-team SageMaker Domains and Kubernetes namespaces for isolation, HyperPod Task Governance for fairness, and namespace-level cost allocation for chargeback.