sincecutoff.com
← all changes

github-mcp-server UI-enabled write tools add show_ui

Introduced 2026-06-18 · score 0.95

HOW TO USE IT

When calling the UI-backed `issue_write` or `create_pull_request` tool with an MCP Apps-capable client, set `show_ui` to `true` to allow the form or `false` to bypass it and execute directly. The parameter is optional and defaults to `true` when available.

issue_write({"method":"create","owner":"<owner>","repo":"<repo>","title":"<title>","show_ui":false})
create_pull_request({"owner":"<owner>","repo":"<repo>","title":"<title>","head":"<branch>","base":"<base-branch>","show_ui":true})

WHY THIS HELPS

When using a UI-enabled write tool, choose whether to show its UI.

BEFORE THIS CHANGE

Before `show_ui`, the server routed these tools to the form based on implicit signals: form submission state and whether the call included parameters the form could not represent. There was no explicit parameter to request direct execution.

REQUIREMENTS AND LIMITATIONS

  • Version: v1.4.0
  • show_ui: Boolean routing flag on `issue_write` and `create_pull_request`: `true` allows the MCP App form; `false` bypasses it for direct execution. Defaults to `true`. Only exposed to clients that advertise MCP App UI support.
  • Prerequisite: `show_ui` is available to clients that advertise MCP App UI support; the supported MCP Apps tools are `issue_write` and `create_pull_request`.
  • Prerequisite: `issue_write` and `create_pull_request` require the GitHub OAuth `repo` scope.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card