From c932179cbf8552ed0e0eadc4ae77a3a5dff02acb Mon Sep 17 00:00:00 2001 From: Cahid Arda Date: Thu, 8 Oct 2026 22:50:55 +0000 Subject: [PATCH] DX-3022: mcp-toolkit README: what's next, the native Tasks path Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01Gtucop3k8CNVLjgvoDTC8n --- packages/mcp-toolkit/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/packages/mcp-toolkit/README.md b/packages/mcp-toolkit/README.md index ca6a0bf..462cd16 100644 --- a/packages/mcp-toolkit/README.md +++ b/packages/mcp-toolkit/README.md @@ -266,6 +266,14 @@ don't depend on the tools, so an adapter for the extension can serve the same re +### What's next: the native path + +Polling through tools costs the model a few turns; the native extension doesn't, which makes it the +right long-term shape. The task record and the execution sit behind two small interfaces, a +`TaskStore` and a `TaskDispatcher`, and the task object already has the extension's shape, so once +clients declare `io.modelcontextprotocol/tasks` a native adapter can serve the same records over +`tasks/get` and keep the tools for everyone else. + ## Events ```ts