The Model Context Protocol (MCP) has released its latest specification, MCP 2026-07-28, which introduces significant changes to how agent costs are tracked. Key updates include the removal of the session primitive, making each request self-describing and eliminating the need for sticky sessions. This change shifts the responsibility of defining budget scopes to the application layer, requiring developers to explicitly manage session IDs or agent run IDs for cost tracking. Additionally, the new Tasks extension allows for asynchronous execution of agent work, meaning cost accumulation occurs independently of the initial request, necessitating a revised approach to budget monitoring during task polling. AI
IMPACT Developers must update their applications to explicitly manage session scopes and monitor costs during asynchronous task execution.
RANK_REASON This is a specification update for a protocol related to AI agent development, impacting how developers manage costs.
AI-generated summary · Google Gemini · from 1 sources. How we write summaries →
