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

Aperta
#3,455 1 commento 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
34.4k
Fork
5.3k
Merge medio
3g 10h
PR unite (30g)
11

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/github-mcp-server

Tutte le issue di github/github-mcp-server

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.