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

Aberta
#3,455 1 comentário 2 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
34.4k
Forks
5.3k
Merge médio
3d 10h
PRs com merge (30d)
11

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/github-mcp-server

Todas as issues de github/github-mcp-server

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.