Insiders Feedback: MCP Apps: issue_write form widget collapses immediately in Claude clients — parameters never hydrate, submit impossible

[M-H-H-B]

Version: Insiders — remote hosted GitHub MCP Server via the Claude connector
(claude.ai / Claude Desktop); no local docker instance, server version not
exposed to the client. Observed 2026-07-06.

Feature: MCP Apps — interactive form widgets (issue_write, presumably all
elicitation-type forms)

Feedback:

Calling issue_write (both method: create and method: update, with fully
pre-filled owner/repo/title/body) renders the interactive form for a split
second, then it collapses into an error state (red warning icon on the
tool-call row). Hovering the collapsed widget shows the server's instruction
text as an error tooltip ("An interactive form has been shown to the user …
Wait silently for the user to review and click Submit.").

During the brief moment the form was visible, it was the blank create
form — no repository pre-selected, empty title and description — although
the call was method: update with issue_number and a pre-filled title.
Tool-call parameters never reach the widget, and edit mode is never entered.

Steps to reproduce:

1. Connect the GitHub MCP server to Claude (claude.ai or Desktop).
2. Model calls issue_write with method: update, owner/repo/issue_number
   and pre-filled title/body.
3. Form flashes (blank, create-mode), then auto-collapses to error state.
4. Same result with method: create and a short pre-filled title/body.

Expected: form stays open, hydrated with the tool-call parameters (edit mode
for update), waiting for user review and submit.
Actual: blank create form, no hydration, auto-collapse. Submit unreachable —
the write never happens.

Reproducibility: 4/4 in one session (2× update ~4.5 KB body, 1× update
title-only, 1× create short) — payload-independent. Display-type MCP Apps
widgets (get_me) render fine in the same session, so the failure is
specific to form widgets, not MCP Apps infrastructure. Screenshots available.

[M-H-H-B]

Additional context after searching the release notes:

• Skip MCP App form when issue/PR write carries non-form params #2589 ("Skip MCP App form when issue/PR write carries non-form params") should already cover this exact call pattern - the remote hosted server apparently still serves a pre-Skip MCP App form when issue/PR write carries non-form params #2589 build, since the form is rendered (blank) instead of being skipped.
• The tool schema exposed to the Claude connector has no show_ui parameter (Add explicit show_ui parameter to UI-enabled write tools #2601), consistent with the remote lagging behind.
• Discussion Introducing MCP Apps Support in Insiders Mode #2048 lists remote-MCP compatibility as actively-worked-on - this report is a concrete repro for that path (Claude remote connector).

So likely: remote deployment lag + form hydration failing over remote, rather than a new client-side bug.