[FEATURE] Desktop Code tab: let users trust domains so MCP App links skip the "Open external link" prompt

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

In the Desktop Code tab, a link clicked inside an MCP App widget raises the "Open external link" prompt unless the connector's publisher has allowlisted the destination.
With the Atlassian directory connector, the createJiraIssue card links to https://<tenant>.atlassian.net/browse/KEY, so opening each issue Claude files takes an extra confirmation click, always for the same site.

The publisher allowlist cannot cover this case.
A directory listing's "Allowed link URIs" field matches exact hostnames ("Subdomains don't match implicitly, so list each one you need"), so a multi-tenant service whose links point at per-customer subdomains would need one entry per customer.
Custom connectors and locally configured servers always show the prompt, and neither users nor organization admins have a setting for it.

Proposed Solution

A list of trusted link destinations under the user's control, applied to MCP App ui/open-link requests:

• an "Always open links to this site" checkbox on the prompt, which adds the host to the list;
• the list shown and editable in Settings;
• a managed setting, so organization admins can pre-approve hosts (for example the company's own Jira site) or stop users from adding their own;
• the matching rules the publisher allowlist already uses (https only, scheme and hostname), plus an optional leading wildcard such as https://*.example.com.

Alternative Solutions

• Accept a leading-wildcard entry such as https://*.atlassian.net in a directory listing's "Allowed link URIs", so publishers of multi-tenant services can cover every customer site.

This fixes the case without a user setting, but only for directory connectors.

• A per-connector "Open this connector's links without asking" toggle.

Coarser than a host list, since it trusts every destination the widget can produce.

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

1. In the Code tab, ask Claude to file a Jira issue; the Atlassian connector renders its createJiraIssue card.
2. Click the issue key in the card: the "Open external link" prompt appears for https://<tenant>.atlassian.net/browse/KEY; click "Open link".
3. The same happens for every issue, every action, in every session, for the same site.

With the change, the first prompt offers to always open links to <tenant>.atlassian.net, and later clicks open directly.

Additional Context

• Documentation: Open external links from MCP Apps and Allowed link URIs.
• Related, but about where links open rather than the prompt: https://github.com/anthropics/claude-code/issues/97995
• Claude desktop app 2.19675.1, macOS 27.0.1, Code tab, Atlassian connector from the Connectors Directory.