-
Notifications
You must be signed in to change notification settings - Fork 1.9k
docs: recategorize Tasks as a protocol extension #3036
Copy link
Copy link
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationrc-high-priorityRelated to an upcoming specification release and needs to be addressed with a high priority.Related to an upcoming specification release and needs to be addressed with a high priority.trackingTracks agreed-upon work (from SEP, WG, or maintainer sync)Tracks agreed-upon work (from SEP, WG, or maintainer sync)
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationrc-high-priorityRelated to an upcoming specification release and needs to be addressed with a high priority.Related to an upcoming specification release and needs to be addressed with a high priority.trackingTracks agreed-upon work (from SEP, WG, or maintainer sync)Tracks agreed-upon work (from SEP, WG, or maintainer sync)
Where was this agreed?
Requested by maintainer David Soria Parra as part of preparing the modelcontextprotocol.io documentation for the 2026-07-28 specification release.
Description
Tasks were introduced experimentally and have moved to an official extension for the 2026-07-28 spec release. Docs still list Tasks as a core (experimental) utility.
Files to update:
docs/docs/learn/architecture.mdx— stop listing "Tasks (Experimental)" as a core utility (line 140); link/extensions/tasks/overviewdocs/community/sdk-tiers.mdx— recategorize Tasks (line 28) as a protocol extension alongside MCP AppsPart of the 2026-07-28 release documentation tracking (milestone: 2026-07-28 Specification Release).