Skip to content

DX-3022: mcp-toolkit README: what's next, the native Tasks path #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
CahidArda wants to merge 1 commit into from
Closed

DX-3022: mcp-toolkit README: what's next, the native Tasks path #63

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions packages/mcp-toolkit/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,6 +266,14 @@ don't depend on the tools, so an adapter for the extension can serve the same re

</details>

### 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
Expand Down
Loading