You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There doesn't seem to be a central ticket for all SDK implementations of a particular change, so sharing this here for SEP-1686 -- the following revisions have been merged on top of the base specification PR for tasks:
Remove an incorrectly-added field from notifications/cancelled: PR
Adjust schema to better-communicate where tasks are valid: PR
Rename/move annotations.taskHint to execution.taskSupport, tweak its enum values, and change a SHOULD to a MUST for the behavior when this is declared:
The actual functional changes should be limited to taskHint, but the rest should help clarify some details around polling.
To save the trouble of going through each of the above PRs one by one, you can also go to the file on the "Files changed" tab here, searching for docs/specification/draft/basic/utilities/tasks.mdx, and then using the "Display the rich diff" button, as shown:
@scottslewis, I have implemented it at work, but there are quite a few more to do. You can use my schema PR as a starting point.
The schema pr doesn't appear to have enough to work with. I would like a working impl of the 11-2025 spec to demonstrate the use of Groups to arrange Tasks...alongside tools, resources, and prompts into collections. Any prediction of when that will be available?
@scottslewis sorry, missed this - I think there's no ETA right now due to low maintainer capacity, but @maschnetwork was looking at this, last I heard.
Our current implementation in production relies on a database, but an open-source implementation should be memory-based. Perhaps you could try using a TypeScript or Python implementation for the demo? @scottslewis
Activity
LucaButBoring commentedon Nov 21, 2025
Relaying here from
#general-sdk-dev:LucaButBoring commentedon Nov 24, 2025
One very last change (we're doing a hard cutoff on additional changes here): adding a
lastUpdatedAtto theTaskobject: modelcontextprotocol/modelcontextprotocol#1875scottslewis commentedon Dec 9, 2025
Any info about plan and/or impl progress?
He-Pin commentedon Dec 10, 2025
@scottslewis, I have implemented it at work, but there are quite a few more to do. You can use my schema PR as a starting point.
scottslewis commentedon Dec 10, 2025
The schema pr doesn't appear to have enough to work with. I would like a working impl of the 11-2025 spec to demonstrate the use of Groups to arrange Tasks...alongside tools, resources, and prompts into collections. Any prediction of when that will be available?
LucaButBoring commentedon Dec 12, 2025
@scottslewis sorry, missed this - I think there's no ETA right now due to low maintainer capacity, but @maschnetwork was looking at this, last I heard.
He-Pin commentedon Dec 13, 2025
Our current implementation in production relies on a database, but an open-source implementation should be memory-based. Perhaps you could try using a TypeScript or Python implementation for the demo?
@scottslewis
LucaButBoring commentedon Dec 17, 2025
I just heard that Max is actually at capacity handling other projects concurrently with this - figuring out if someone else can take this on.
LucaButBoring commentedon Jan 15, 2026
I'm taking this one
bored-tomato commentedon Mar 31, 2026
Hi @LucaButBoring,
Not sure if this question has been asked, but are there any plans to support task-augmented tools in stateless MCP servers?