Per-server "collapse by default" for MCP Apps (Atlassian's Jira cards take over Claude threads)

[adrianorocha-dev]

What happened

Since #29803, Claude threads render MCP Apps inline. Atlassian's MCP server attaches an app to its Jira tools that renders a full issue view: the whole description, acceptance criteria, and so on. It asks for a height large enough to fit all of it, on every call. In a single "refine this ticket" turn, that meant the main issue plus one card per linked issue, each up to 2,000px tall with its own scroll bar. The assistant's reply ended up spread between them.

T3 Code renders what the app asks for, so this is mainly Atlassian's design. But we can't change third-party apps, and as more MCP servers ship apps, users need a way to rein in the ones that don't behave.

Diagnosis

In McpAppFrame, the host provides no close or collapse control: its only button is "Exit full screen", and a card closes only when the app requests teardown. Nothing in settings or per server turns rendering off either. Cards grow to whatever height the app reports, up to MCP_APP_MAX_HEIGHT (2000). Other timeline rows, such as the changed-files section, can already be collapsed.

Proposal

A per-server "collapse by default" list in settings (a list of shame, if you will):

• Apps from listed servers render as a one-line collapsed row (server, tool, expand button) instead of an inline card.
• Expanding shows the app as it does today. Ideally there's also a "Collapse apps from this server" action on the card itself, so you don't have to dig through settings.
• Everything else stays as it is, so well-behaved apps keep rendering inline.

A host-side collapse button on every card would be useful on its own too, but the per-server default is what keeps a thread usable without clicking six times.

Steps to reproduce

1. Server on 0.1.8-nightly.20261105.4205 or later, Claude Code 2.1.301 or later.
2. Connect the Atlassian MCP connector.
3. In a Claude thread: "help me refine ABC-123 so it is ready to build".
4. Each Jira tool call renders as a tall inline Jira card.

Version

0.1.8-nightly.20261105.4218 (remote server background service and desktop app).

Environment

Desktop app on macOS (arm64) connected to a remote Linux server running as a background service. Claude Code 2.1.318.

Evidence

Screenshot withheld because it contains private work content. One turn produced six stacked Jira cards, each scrolling on its own.

Related issues

#29803

Fix applied or workaround

None. The only workaround is downgrading T3 Code or the Claude CLI.

Filed by

Triaged with Claude Opus 5.5 (claude-opus-5-5) in Claude Code, via t3 triage.

[Niklas-Mezynski]

Same here with the claude.ai Trello connector: every trelloReadCard/board read in a Claude thread now renders an inline Trello widget (ui://widget/trello-widget.html), so agent tasks that read cards in the background fill the thread with cards nobody asked to see.

+1 for per-server "collapse by default". A global "don't render MCP Apps inline" toggle would also help: in agent workflows the tool result is for the model, and the widget is rarely useful to the person.

T3 Code Nightly 0.1.8-nightly.20261105.4205, desktop on macOS 27.0.1 (arm64), Claude provider (Opus 5.5) via Claude Code.

[JulienZD]

Related discussion with redacted images showing how big the Jira MCP app cards are

[oryan-block]

Same on stable 0.1.8, desktop app on macOS (arm64) running its own local backend, Claude provider (Claude Fable 5.2). The agent calls getJiraIssue on a ticket just to read it for context, and the Atlassian widget (ui://widget/jira-widget.html) renders as a full inline card with the whole description, one card per call. In one turn it fetched two sibling tickets back to back, and the two stacked cards pushed the actual work out of view.

Confirmed in the v0.1.8 source: McpAppFrame has no host-side collapse, and the card height follows the app's size request up to MCP_APP_MAX_HEIGHT (2000).

+1 for collapsed by default: a one-line row (server, tool, the issue key or title if available) that expands into the app as it renders today. Collapsing every MCP App by default would cover my case. A per-server list would be fine too.

Triaged with Claude Opus 5.5 (claude-opus-5-5) in Claude Code, via t3 triage.

[jjliggett]

Hi! Claude Sonnet here, on behalf of @jjliggett. 👋

Thank you for filing this, and thanks to everyone who has added examples. Adding another data point from stable, in case it helps with prioritizing.

Environment: T3 Code 0.1.9 (stable), desktop on Linux, Claude provider, Claude Code 2.1.311. Both the claude.ai "Atlassian Rovo" and "JIRA mcp" connectors are enabled. We noticed the cards right after updating from before 0.1.8, which lines up with #29803 (MCP Apps rendering in Claude threads) landing.

What it looks like: one working thread in our workspace now holds 37 inline Jira cards. The tools involved:

Tool | Cards -- | -- transitionJiraIssue | 10 getJiraIssue | 9 searchJiraIssuesUsingJql | 8 createJiraIssue | 7 editJiraIssue | 3

A few things stand out beyond the height already reported here:

• Write calls (transitionJiraIssue, editJiraIssue, createJiraIssue) render a full card, even though the agent's one-line reply already says what happened. The card adds nothing, but it takes the space of a whole ticket.
• Search results render a card per call, so a single "find related tickets" turn pushes the actual answer a few screens down.
• Each card carries the ticket's full description. The thread becomes hard to scan, and the cards read as noise next to the plan the agent is writing.

What we'd find most useful, in line with the proposals above (the choice of shape is of course the maintainers'):

• A host-side collapse button on every card, even if nothing else ships.
• A one-line collapsed row (server, tool, issue key or title) that expands to today's card.
• A per-server "collapse by default" list, and/or a global "don't render MCP Apps inline" switch. For agent workflows the tool result is mostly for the model, so a global opt-out would also cover the Trello case mentioned earlier.