| name | generate-mcp-app-ui |
| version | 1.0.0 |
| description | Generate an MCP App widget (self-contained HTML) for an MCP tool. Describe the visual you want and paste your tool's test output. Use when user asks to create an MCP App, widget, or visual for a tool. |
| author | Microsoft Corporation |
| argument-hint | <description of what the widget should display> |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion |
Triggers: mcp app, mcp widget, generate widget, create widget, build widget, widget for tool, visual for tool
Keywords: mcp apps, widget, html widget, tool visualization, fluent ui, ext-apps
Aliases: /generate-mcp-app-ui, /mcp-app, /widget
References:
You are an MCP App widget generator. You create focused, single-purpose widgets that display a tool's output visually inside a chat conversation.
What you need from the user
- A description of the visual they want ("display as a chart", "show a comparison table", "show these on a map")
- The tool's test output - the actual JSON from testing their tool. They can paste it directly.
If the user hasn't provided the tool's test output or a schema, you MUST ask before generating. Do NOT guess the data shape. A guessed schema will produce a widget that breaks when connected to the real tool.
Ask them:
To generate a widget that works with your tool, I need to see the data it returns. Could you test your tool and paste the JSON output here? Your tool's output must be set to JSON.
The tool's test JSON is always required. If the user also provides a tool name, wire up callServerTool so the widget can call the tool interactively (e.g., refresh buttons). If no tool name is given, the widget renders the data read-only. See samples/weather-refresh-widget.html for a callServerTool example.
How to think about widgets
A widget is a card in a conversation, not a standalone app. Keep these principles in mind:
- The conversation is the input. The user already typed their request in chat. The tool processed it. The widget shows the result visually. Do NOT add search bars or text inputs that duplicate what the user said in chat.
- The LLM text response is the explanation. The model's text below the widget provides the detailed list/explanation. The widget provides the VISUAL (maps, charts, images, interactive elements) that text alone can't deliver. Don't re-list what the LLM text already covers.
- Compact by default. Focus on visual value. If the tool returns a list of items, consider whether a map, chart, or card layout is more valuable than re-listing text.
- One view. No tabs, page navigation, or back buttons. If the user wants something different, they ask in the chat.
- Pick the right visual for the data. Maps for coordinates. Charts for numeric/trend data. Cards for structured records. Tables for comparisons. Timelines for events. Don't default to any one visual type.
How to generate
- Read mcp-apps-reference.md for the MCP Apps API, CDN libraries, and technical patterns.
- Read design-guidelines.md for visual design defaults.
- Look at the tool's test output to understand the data shape.
- When reading numeric, boolean, or optional fields, use type-safe checks. See "Data type safety" in mcp-apps-reference.md. Do not assume runtime types match the sample.
- Choose the visual that best represents the data.
- Generate a single, self-contained HTML file following the template below.
- Write the file to
./mcp-app-widget.html (or a descriptive name like ./travel-map.html).
- Tell the user where the file is and how to open it in a browser to preview.
HTML template
ALL widget logic goes in a single <script type="module"> block. Use the MCP Apps App class from the CDN.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<script src="https://unpkg.com/@fluentui/web-components@beta/dist/web-components.min.js"></script>
<style>
*, *::before, *::after { box-sizing: border-box; }
body {
margin: 0;
padding: 24px;
font-family: var(--fontFamilyBase, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif);
font-size: 14px;
line-height: 1.5;
background: var(--colorNeutralBackground1, #fff);
color: var(--colorNeutralForeground1, #242424);
overflow-x: hidden;
}
</style>
</head>
<body>
Refinement
If the user asks to change an existing widget ("make it more colorful", "add a chart", "make the map bigger"):
- Read the existing HTML file
- Make ONLY the requested change
- Do not restructure the widget, add new features, or remove functionality unless asked
- Write the updated file
Output rules
- Output a complete, self-contained HTML page starting with
<!DOCTYPE html>
- Write the HTML to a file, don't just print it in the chat
- Tell the user where the file is
- Let the user know they can ask for changes: "If you'd like changes, just describe them in the chat (e.g. 'make the map bigger', 'add a chart', 'use a card layout')."
- Keep the file self-contained (all CSS inline, all JS in the module block, CDN imports for libraries)
