The MCP specification just went stateless. Clare Liguori — Senior Principal Engineer at AWS and core MCP maintainer — explains what changed, why it matters, and what it unlocks for agent developers building with Strands Agents and Kiro. In this episode, Romain sits down with Clare Liguori, Senior Principal Engineer at AWS, to discuss the July 28 MCP spec release, new MCP extensions (Skills, Tasks, Events), Strands Agents Harness SDK, Strands Shell, Physical AI in Strands Labs, and the latest Kiro updates across Web, CLI, IDE 1.0, and iOS. Key takeaways: • MCP goes stateless — the July 28 spec release removes the need for stateful streaming in remote MCP servers, so SaaS providers can drop sticky sessions and load-balancer gymnastics and run each request anywhere. Expect a new wave of remote MCP servers over HTTP. • New MCP extensions framework — features now start as stable extensions before graduating into the official spec: Skills over MCP (bundle a workflow and its tools together), long-running Tasks (kick off builds or jobs without blocking the agent), and Events (trigger always-on agents from external signals like Slack or an earthquake feed). • Strands Agents Harness SDK & TypeScript 1.0 — a more batteries-included harness with context management, compaction, and excellent out-of-the-box file tools, plus the TypeScript SDK reaching 1.0. Upgrade the model ID and your agent gets better. • Strands Shell — a lightweight, in-process agent sandbox written in Rust (cross-platform, Python SDK today). It gives an agent a virtual file system and minimal bash/Lua scripting without a heavyweight VM — great as a safe scratch pad or for scripting tools together. • Strands Labs & Physical AI — an experimental space for bleeding-edge agent ideas, including combining low-latency local VLA models on robots with the long-range, multi-task reasoning of frontier models in the cloud. • AgentCore Managed Harness — a configuration-based way to run agents (prompt, model, Lambda tools, context and session management) that is Strands under the hood, no Python or TypeScript required. AgentCore Gateway added MCP 2026-07-28 support day one, with version negotiation for backward compatibility. • One unified Kiro harness — Kiro Web, iOS, CLI, and IDE 1.0 now share one harness, bringing spec-driven development, hooks, skills, and powers to every client and letting new features ship across clients on the same day. • Automated reasoning in specs — property-based testing plus ambiguity and conflict detection in requirements help you express intent clearly; the permission system is built on Cedar with policy presets like dev shell, trust all, and read all. • Right-sizing specs and collaborating — check specs into code as a snapshot of intent, watch design and task-list length as a signal to split into multiple specs, add per-task validation steps, and collaborate on specs with comments in Kiro Web.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related