---
title: "MCP Apps: interactive Linkbreakers cards inside Claude and ChatGPT"
description: "The Linkbreakers MCP server renders link, QR code, visitor and workspace cards inside AI conversations with MCP Apps (ui:// resources, SEP-1865) and the OpenAI Apps SDK. Which tools render UI, how it works and how it stays safe."
canonical: "https://linkbreakers.com/help/article/mcp-apps-interactive-ui"
last-updated: 2026-10-10
---

# MCP Apps: interactive Linkbreakers cards inside Claude and ChatGPT

> The Linkbreakers MCP server renders link, QR code, visitor and workspace cards inside AI conversations with MCP Apps (ui:// resources, SEP-1865) and the OpenAI Apps SDK. Which tools render UI, how it works and how it stays safe.

## Short answer

The Linkbreakers MCP server supports **MCP Apps**, the official MCP extension for interactive UI (`io.modelcontextprotocol/ui`, SEP-1865). When an AI client that supports it, such as Claude or ChatGPT, calls certain Linkbreakers tools, it shows a Linkbreakers card in the conversation: a link with its scannable QR code, a list of visitors, or your workspace totals. Clients without MCP Apps support receive the same result as text, so nothing breaks.

## Quick summary

- MCP server: `https://mcp.linkbreakers.com` (OAuth or an API token), see [MCP server setup](/help/article/mcp-server-setup)
- `links_create`, `links_get` → link card at `ui://linkbreakers/link-card.html`
- `visitors_list` → visitors card at `ui://linkbreakers/visitors-card.html`
- `metrics_workspace` → workspace card at `ui://linkbreakers/workspace-metrics.html`
- Each tool carries `_meta.ui.resourceUri` and ChatGPT's `openai/outputTemplate` alias in `tools/list`
- Views are `text/html;profile=mcp-app` resources served by `resources/read`, self-contained, with no external scripts
- The views follow the host's light or dark theme
- The public docs MCP server (`https://linkbreakers.com/mcp`, no sign-in) renders `search_docs` results as a list of clickable articles at `ui://linkbreakers-docs/search-results.html`

## What each card shows

**Link card.** The link's name, its QR code, the short link and destination (both clickable), creation and expiry dates, tags and the number of scans. Buttons open the link's analytics and its QR design in the dashboard. The QR code is the link's own designed image when the tool returned it, and otherwise is drawn from the short link in the card itself.

**Visitors card.** How many visitors match, the visits on the page shown, how many are identified, and the most recent visitors with their visit, QR code and device counts and up to three attributes they gave. Each row opens the visitor in the dashboard.

**Workspace card.** Links, scans of all time and this month, members, folders and QR templates, plus credit usage for the current cycle.

## How it works

The MCP server announces the `io.modelcontextprotocol/ui` extension in `initialize`. In `tools/list`, the tools above name their view in `_meta.ui.resourceUri`. The client reads the view once with `resources/read` and renders it in a sandboxed iframe. After the tool runs, the client hands the tool result to the view, which draws it.

The link between a tool and its view is declared once, on the API definition of the tool, and the server refuses to start if a tool points at a view it does not serve. The [Server Card](https://mcp.linkbreakers.com/.well-known/mcp/server-card.json) lists the views too, so clients can see them before connecting.

## Security

- The views are static HTML with inline styles and scripts. They load nothing from other domains, except the link card, which may display the QR image from `assets.linkbreakers.com`, the only origin it declares in its content security policy
- They contain no credentials. Data reaches a view only through the tool result the client already received
- Text from your workspace is written as text, never as HTML
- Links open through the client (`ui/open-link`), which can ask you first

## Frequently asked questions

### Which clients show the cards?

Any client that implements MCP Apps, including Claude and ChatGPT. Other clients, such as many code editors, show the tool result as text.

### Can the cards change my data?

No. They only display the result of the tool the model already called, and open links in your browser when you click them.

### Can I try it without touching my workspace?

Yes. Connect the MCP server with a [sandbox](/help/article/sandbox-test-environment) token, create a link, and the link card renders the sandbox link.