Remote MCP tools missing ui/resourceUri in _meta - Claude Desktop widgets no longer render

[Rory Penman]

Since around a month ago, the tools exposed by the Atlassian Remote MCP Server (mcp.atlassian.com) no longer include a `ui/resourceUri` field in their `_meta` block.

Claude Desktop uses this field to render rich in-chat widgets for tool results. Without it, the app logs a warning per tool and falls back to plain text output. Example warnings:

- Tool getJiraIssue has no UI resource (no ui/resourceUri in tool._meta)
- Tool editJiraIssue has no UI resource (no ui/resourceUri in tool._meta)
- Tool transitionJiraIssue has no UI resource (no ui/resourceUri in tool._meta)
- Tool searchJiraIssuesUsingJql has no UI resource (no ui/resourceUri in tool._meta)

The tools themselves still work correctly - this is a UI/UX regression only.

Questions:
1. Was `ui/resourceUri` intentionally removed from tool metadata in a recent deploy?
2. If not, is it on the roadmap to restore it?
3. If yes (removed intentionally), is there a replacement mechanism for client-side widget rendering?

Client: Claude Desktop (via mcp-remote OAuth)
Cloud site: salaryfinance.atlassian.net

[Alexandre Pezzini]

The issue you're describing is a known regression affecting the Atlassian Remote MCP Server (mcp.atlassian.com).

Based on recent reports from the developer community and internal tracking, here is the current status of this behavior:

1. Was ui/resourceUri intentionally removed?

It appears to be a regression rather than an intentional permanent removal. The server is currently advertising widget resources (like ui://widget/jira-widget.html) in the resources/list call, but failing to fulfill the resources/read request with a -32601: Method not found error.

Because the ui/resourceUri is missing from the _meta block of the tool definitions, Claude Desktop cannot map the tool result to the corresponding rich widget, causing the fallback to plain text and the warnings you're seeing. This is currently being tracked under https://jira.atlassian.com/browse/ROVO-963.

2. Is it on the roadmap to restore it?

Yes. This has been flagged as a high-priority UI/UX bug because it breaks the "Rich UI" experience that is a core part of the Atlassian MCP offering for partners like Anthropic (Claude) and Cursor.

The engineering teams are working on aligning the MCP Apps specification (which handles these rich widgets) with the remote server's production environment. The goal is to restore the ui/resourceUri metadata so that interactive cards for Jira issues and Confluence pages render correctly again.

3. Current Workaround / Status

• Functionality: As you noted, the tools themselves (searching, creating, and transitioning issues) remain fully functional. Only the visual "widget" representation is affected.

• Tracking: You can monitor the progress and receive updates by watching the public tracker here: https://jira.atlassian.com/browse/ROVO-963. Additionally, you can follow the discussion on the official repository: MCP Apps widget resources advertised in resources/list but resources/read returns -32601 · Issue #186 · atlassian/atlassian-mcp-server.

• Recommendation: Ensure your Claude Desktop is using the latest remote configuration. If you are using a local npx version of the server, running npx clear-npx-cache and restarting might help once the fix is published to the @atlassian/mcp-server package.

Please be sure to Vote and Watch the ROVO ticket linked above to stay informed on the fix deployment.