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

Abierto
#3,455 1 comentario 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
34.4k
Forks
5.3k
Merge medio
3 d 10 h
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/github-mcp-server

Todos los issues de github/github-mcp-server

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.