Skip to content

[backport] Fix issue_write MCP App form gating for labels/assignees/milestone/type (upstream main) #20

Description

@gastrodon

Summary

issue_write's form-gating logic uses issueWriteFormParams to decide whether to show the MCP App form or execute directly: a call with any parameter outside the allowlist bypasses the form. The form pre-fills and re-submits labels, assignees, milestone, and type, but those four were absent from the allowlist — so any call passing them skipped the confirmation UI.

Fix: add labels, assignees, milestone, and type to issueWriteFormParams. The allowlist now covers every property in the current input schema, leaving issueWriteHasNonFormParams as a forward-compatibility safety net for future properties added without form support.

Also corrects inaccurate tool description text on issue_write and create_pull_request that claimed the form did not collect fields it actually does.

Upstream reference

Fork conflict

None. The fork does not use MCP Apps UI for its custom tools.

Context

Agents calling issue_write with label or assignee changes were bypassing the confirmation form silently, undermining the user-confirmation guarantee that MCP Apps is designed to provide.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backportBackport from upstreambugSomething isn't workingno-opFork already has equivalent functionality

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions