Feature request: setting to disable MCP widget (MCP Apps) rendering per-connector
Feature request: per-connector toggle to disable MCP widget (MCP Apps / UI resource) rendering
Summary
When an MCP connector declares a UI resource via _meta.ui (aka "MCP Apps"), Claude Desktop / claude.ai automatically renders an interactive widget for every matching tool call. For the Atlassian/Rovo connector, this means every searchJiraIssuesUsingJql or getJiraIssue call renders a rich card widget (avatars, status pills, checkboxes, "Open in Jira" link, full ticket body) instead of plain text.
Problem
For users who read/process a lot of Jira issues through Claude (e.g. bulk searches, audits, status syncs), this widget rendering is more disruptive than helpful:
- It takes up much more vertical space than a plain-text/JSON summary for the same information.
- It duplicates content Claude already summarizes in its own reply.
- There is currently no way to opt out of it while keeping the underlying MCP tool functional. The only workaround is to disable the entire connector (
claude mcp disable <name>), which removes tool access entirely, not just the widget.
Requested feature
A per-connector (or global) setting to render MCP tool results as plain text/JSON instead of invoking the declared UI resource widget, without disabling the connector's tools. Ideally exposed as a toggle in Claude Desktop / claude.ai connector settings, and/or a Claude Code CLI equivalent (e.g. claude mcp configure <name> --no-widgets or similar).
Environment
- Reported via Claude Desktop / claude.ai (not the terminal CLI) — screenshots show the "Widget from Atlassian Rovo
searchJiraIssuesUsingJql" / "Widget from Atlassian RovogetJiraIssue" cards. - Connector: Atlassian Rovo MCP (Jira/Confluence).
3 Comments
+1 - the preview on every JQL search is very annoying and distracting.
Same connector here (claude.ai Atlassian, Jira results), with a mechanism note and a second symptom that may be the more actionable half.
The widget's expanded state is a plain
useState(true)per widget instance in the desktop renderer — no persistence, and no settings key matching widget/collapse/expand exists in the settings schema. So a widget cannot be kept collapsed even manually: collapsing it doesn't stick across renders.The consequence beyond vertical space: in a long session the re-expansion jumps the transcript and destroys scroll position while I'm reading earlier turns. That makes it a scroll-anchoring bug, not only a density preference — same class as #83418 and #82703.
So the ask splits in two, and the second is cheap and independent of the per-connector plumbing this issue requests:
Environment: Claude desktop app, macOS 15.5 (Darwin 25.5.0).
Current workaround is "Block nonessential services" (Settings → Telemetry & updates), which blocks the widget iframe origin but also stops artifacts rendering and removes connector icons — too blunt to live with.
+1 I find this very annoying as well.