← All IntelClip / Developer ToolsWhy no agent client supports MCP tasks yet
From MCP Tasks (async): Why Aren't Any Agents Supporting Them? — Cornelia Davis, Temporal · ≈0:30
Explains the adoption gap in the async-tool part of MCP: the spec shipped experimental and is complex enough that client authors rationally waited for a revision.
What’s in it
- Explains the adoption gap in the async-tool part of MCP: the spec shipped experimental and is complex enough that client authors rationally waited for a revision.
Clip transcript
moment. But, the first answer to that question is, well, cuz they're smart. The people who are building those clients are smart. What I mean by that is that the MCP tasks specification that came out in November was marked as experimental. And so, well, you might shrug and say, well, gosh, those clients and servers, they're all supporting a whole bunch of experimental things. Why not MCP tasks? Well, again, you'll see the answer to that as we move forward. Um the next answer to that question is, well, they're pretty involved. Um there's a lot of complexity in here, and that's what I want to do over the next 20 minutes is teach you some of that complexity.
Comments
Checking sign-in…
Loading comments…