Keep an opt-out for MCP Apps form deferral on the hosted remote server

未關閉
#3,455 1 則留言 2 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
go

研究方向

Start by tracing where the server configures MCP Apps form deferral and handles mcp_apps_disable_form_deferral, then check how the hosted api.githubcopilot.com/mcp endpoint exposes configuration to clients that cannot send feature headers or query parameters. Compare the behavior with the referenced issues #2589, #2823, and #3415. Done means clients with non-rendering forms have a documented, usable opt-out or fallback; the issue leaves the implementation choice open.

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

描述

PR #3348 removed the remote_mcp_ui_apps flag and made MCP Apps form deferral unconditional for UI-capable clients. Write tools such as issue_write and create_pull_request now hand off to a form before executing.

On claude.ai the form never renders. The write is deferred, nothing appears in the conversation, and the assistant reports that a form is waiting for review and submission — so the call silently does nothing and the user is told to act on a widget that is not there. Issue creation that worked previously no longer does. #3415 reports the same non-rendering; #2823 proposes a capability negotiation gap, which fits: the client appears to advertise UI support well enough for the server to defer, but does not render this app's form.

I have not verified that #3348 is the cause in my case, so this is a request about the configuration surface rather than a bug report.

The request: please keep a usable opt-out.

  • Confirm whether mcp_apps_disable_form_deferral is honoured on api.githubcopilot.com/mcp, and document how to set it for clients that cannot send X-MCP-Features or a ?features= query (managed connectors, for example).
  • Consider not deferring when the write call already carries complete parameters, along the lines of #2589.
  • Consider falling back to direct execution when the form is never acknowledged by the client.

As it stands, a client whose form never renders has no path back to direct execution, since the flag-based opt-out no longer exists.

主要語言
Go
星號
34.4k
分支
5.3k
平均合併
3 天 10 小時
30 天內合併 PR
11

環境準備

從這裡開始

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

github/github-mcp-server 的其他 Issue

查看 github/github-mcp-server 的全部 Issue

相似的 Issue

更多 Go Issue

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

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