[dotnet-port-api] Document MCP Tasks extension gap - #960
Open
Michelle Clayton (michelle-clayton-work) wants to merge 2 commits into
Open
[dotnet-port-api] Document MCP Tasks extension gap#960Michelle Clayton (michelle-clayton-work) wants to merge 2 commits into
Michelle Clayton (michelle-clayton-work) wants to merge 2 commits into
Conversation
Update the .NET/Go feature comparison to call out the new .NET MCP Tasks extension surface and the corresponding Go gap in task-aware MCP client tooling. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Michelle Clayton (michelle-clayton-work)
requested a review
from a team
as a code owner
September 1, 2026 20:42
Copilot started reviewing on behalf of
Michelle Clayton (michelle-clayton-work)
September 1, 2026 20:43
View session
github-actions
Bot
added
the
size:small
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The change is a targeted documentation update that cleanly aligns the comparison text with the described upstream .NET Tasks-extension work, with no code or behavioral changes.
Pull request overview
Updates the .NET vs Go SDK feature comparison to reflect the newer .NET MCP Tasks extension surface and explicitly document the current Go-side gap in task-aware MCP client tooling.
Changes:
- Updated the document’s comparison date to August 28, 2026.
- Expanded the “MCP client tools” feature-matrix row to call out .NET’s task-aware wrappers (polling, input requests, best-effort remote cancellation) vs Go’s current basic MCP bridge.
- Added a Hosting/DevEx bullet explicitly stating the Go MCP client bridge does not yet expose Tasks-extension task-aware wrapper behavior.
File summaries
| File | Description |
|---|---|
| docs/dotnet-go-sdk-feature-comparison.md | Documents the .NET MCP Tasks extension capabilities and clarifies the corresponding Go parity gap in MCP client tooling. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
|
Copilot rebase |
…asks-gap-doc-5fb0599bd2d18f28 # Conflicts: # docs/dotnet-go-sdk-feature-comparison.md Co-authored-by: qmuntal <3747816+qmuntal@users.noreply.github.com>
Contributor
Merged the latest |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updated
docs/dotnet-go-sdk-feature-comparison.mdafter reviewing the upstream .NET MCP Tasks extension work in microsoft/agent-framework#7774 and commit96560bbf65973d098e09f38cc69f45826845d08e. The comparison now explicitly records that .NET MCP client tools support task-aware wrappers with polling, input requests, and best-effort remote cancellation, while Go still exposes only the basicmcptool.Connect/ListToolsbridge.I selected a docs realignment rather than a code port because the complete upstream change would require new public Go MCP APIs and lower-level task-extension support that is not yet present in the current Go MCP stack.
Ported .NET PRs
Breaking Changes
No.
Tests and Examples
Notes
#7774,2026-07-28 Tasks extension, orListAgentToolsWithTasks; none was found.github.com/modelcontextprotocol/go-sdk/mcpand currently exposes basic tool listing/invocation plusinput_requiredresult handling, but not task-aware wrapper APIs analogous to .NETMcpTaskOptions/ListAgentToolsWithTasksAsync.Closes #938