Skip to content

TUI has no clipboard/copy affordance at all — no OSC 52 fallback for terminal copy #2421

Closed

Description

@CloneOfAlex

Which version line?

v2 — current (@modelcontextprotocol/inspector@latest)

Which client?

TUI

Inspector version

2.7.0 (git tag) — static code-review finding, not run locally

Node version

N/A — static code review, no live run performed

Operating system (and browser, for the web client)

N/A — static code review

Transport

Not applicable / never connected

MCP server under inspection

N/A — this is a static code-review finding comparing clients/tui against clients/web/src/components/elements/CopyButton in the 2.7.0 tag source, not a live reproduction against a running MCP server.

Steps to reproduce

Found via static review of the 2.7.0 tag source, not a live run.

  1. Web has a dedicated one-click copy affordance (clients/web/src/components/elements/CopyButton/CopyButton.tsx), built on the browser Clipboard API and used throughout the UI (tokens, IDs, secrets via SecretStorageFooter).
  2. Searching clients/tui for "clipboard" (case-insensitive) returns no matches at all.
  3. Searching clients/tui for "osc52" / "OSC 52" / "OSC-52" also returns no matches.

I have not run the TUI over SSH to confirm the absence live; flagging what a repo-wide grep across the 2.7.0 tag source shows.

Expected behavior

The TUI has some way to get a value (an OAuth token, a request/response body, a resource URI) out of the terminal UI and onto the system clipboard, comparable to Web's CopyButton, including over an SSH session where the terminal emulator has no direct access to the remote process's clipboard.

Actual behavior

There appears to be no copy affordance in the TUI at all. The only way to get a value out is manually selecting text with the terminal emulator's own mouse-selection, which does not work over many SSH sessions unless the remote terminal emits OSC 52 escape sequences and the local terminal honors them, and is impractical for anything longer than a short line — the same large-payload problem issue #2407 already flags for the TUI's request/response rendering.

Suggested fix: add a copy affordance to the TUI — at minimum, emit an OSC 52 escape sequence (widely supported over SSH) when the user selects "copy" on a value, with a documented fallback (e.g. printing the raw value to a dedicated line) for terminals that don't support OSC 52.

Logs, errors, or screenshots

No response

Already prototyped a fix?

No response

Before you submit

  • I searched existing issues and this is not a duplicate.
  • This is not a security vulnerability report (those go through the private advisory process).

Activity

  1. added
    v2Issues and PRs for v2
    and removed
    bugSomething isn't working
    on Sep 18, 2026
  2. cliffhall commented on Sep 18, 2026

    @cliffhall
    Member

    Triage: Priority Low (total 4)

    • Severity 2 — missing affordance; terminal selection is the workaround
    • Urgency 2 — wanted eventually
    • Bonuses: none

    Labels applied at triage: v2, enhancement (new feature) — replacing the form's static bug.

    Board: #28, Status Incoming (awaiting maintainer review — no milestone yet).

  3. added this to the v2.10.0 milestone on Sep 23, 2026
  4. self-assigned this
    on Oct 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature requestv2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions