Agents, Workers - Agents SDK v0.6.0: RPC transport for MCP, optional OAuth, hardened schema conversion, and @cloudflare/ai-chat fixes

The latest release of the Agents SDK lets you define an Agent and an McpAgent in the same Worker and connect them over RPC — no HTTP, no network overhead. It also makes OAuth opt-in for simple MCP connections, hardens the schema converter for production workloads, and ships a batch of @cloudflare/ai-chat reliability fixes. RPC transport for MCP You can now connect an Agent to an McpAgent in the same Worker using a Durable Object binding instead of an HTTP URL. The connection stays entirely within the Cloudflare runtime — no network round-trips, no serialization overhead. Pass the Durable Object namespace directly to addMcpServer : JavaScript import { Agent } from "agents" ; export class MyAgent extends Agent { async onStart () { // Connect via DO binding — no HTTP, no network overhead await this . addMcpServer ( "counter" , env . MY_MCP ) ; // With props for per-user context await this . addMcpServer ( "counter" , env . MY_MCP , { props : { userId : "user-123" , role : "admin" }, } ) ; } } TypeScript import { Agent } from "agents" ; export class MyAgent extends Agent { async onStart () { // Connect via DO binding — no HTTP, no network overhead await this . addMcpServer ( "counter" , env . MY_MCP ) ; // With props for per-user context await this . addMcpServer ( "counter" , env . MY_MCP , { props : { userId : "user-123" , role : "admin" }, } ) ; } } The addMcpServer method now accepts string