Docs: stateless.md says the stateful task store is "scoped per session", but Tasks are unavailable in strict Stateful mode

未關閉 適合新手
#2,031 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
1/5
預估耗時
1 小時以內
新手友好度
88/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
csharp, markdown
領域
documentation

研究方向

閱讀 docs/concepts/stateless/stateless.md 第 231 行附近(比較表)和第 686 行(Stateful 模式段落),然後與 docs/concepts/tasks/tasks.md 第 340-342 行比較,那裡已經說明了正確的 down-level 行為。略讀 McpTasksBuilderExtensions.GateToJuly2026OrLaterProtocol 和 StreamableHttpHandler.GetOrCreateSessionAsync 以確認 gating,然後只改寫 Stateful 的儲存格/段落;Stateless 欄保持原樣。完成意味著表格和段落寫明 tasks 需要 2026-07-28 revision,並且在 strict Stateful 模式下不可用。

由索引模型根據 Issue 內容生成。

描述

The comparison table in docs/concepts/stateless/stateless.md (line 231) describes Tasks support as:

| Tasks | Supported — shared task store, no per-session isolation | Supported — task store scoped per session |

and the "Stateful mode" section (line 686) says:

In stateful mode, the IMcpTaskStore tracks tasks created for that server instance.

Both statements describe a stateful task store that the current implementation does not provide:

  • The tasks/get, tasks/update, and tasks/cancel handlers, and task creation in the call-tool filter, are all gated on the 2026-07-28 protocol revision and throw MethodNotFound for any earlier version (McpTasksBuilderExtensions.GateToJuly2026OrLaterProtocol).
  • A Streamable HTTP server running in strict Stateful session mode refuses 2026-07-28 (per-request-metadata) requests before dispatch (StreamableHttpHandler.GetOrCreateSessionAsync), and a session established through the initialize handshake can only negotiate a pre-2026-07-28 version. So in strict Stateful mode no task can be created or accessed at all. (In StatefulForInitializeClients mode, modern requests are instead served statelessly, and tasks work there exactly as in Stateless mode — with the shared, non-isolated store the Stateless column describes.)
  • WithTasks registers the supplied IMcpTaskStore as a single shared instance; there is no per-session scoping mechanism.

docs/concepts/tasks/tasks.md (lines 340-342) already documents the correct behavior for down-level connections ("the v2 server does not create Tasks on a down-level connection, and its tasks/get endpoint rejects the legacy request with a method-not-found error"), so this looks like the stateless.md text simply was not updated when the protocol gating landed.

Suggested fix: change the Stateful cell to reflect that Tasks are not available in strict Stateful mode (they require the 2026-07-28 revision and run on the sessionless path — which is also how they are served under StatefulForInitializeClients), and adjust the "Stateful mode" paragraph accordingly. The Stateless column ("shared task store, no per-session isolation") matches the implementation and needs no change.

主要語言
C#
星號
4.6k
分支
849
平均合併
1 天 16 小時
30 天內合併 PR
24

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

modelcontextprotocol/csharp-sdk 的其他 Issue

查看 modelcontextprotocol/csharp-sdk 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。