generate-mcp-app-ui

根据工具测试输出与视觉要求，生成可嵌入的 MCP App 小组件界面

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "generate-mcp-app-ui" 技能：
1. 下载 https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/mcp-apps/skills/generate-mcp-app-ui/SKILL.md
2. 保存为 ~/.claude/skills/generate-mcp-app-ui/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

为天气工具生成卡片界面

输入

请基于下面的天气工具测试输出，生成一个自包含 HTML 的 MCP App 小组件。风格要求：现代、浅色、卡片式布局，突出当前温度、天气图标、未来三天预报，并适配移动端。测试输出：{"location":"Shanghai","current":{"temp":28,"condition":"Sunny"},"forecast":[{"day":"Mon","high":30,"low":24},{"day":"Tue","high":29,"low":23},{"day":"Wed","high":27,"low":22}]}

预期产出

一个可直接使用的 HTML 小组件，展示当前天气与短期预报，界面美观且响应式

为分析工具生成图表面板

输入

请为这个销售分析 MCP 工具生成一个自包含 HTML 小组件。要求：深色仪表盘风格，包含关键指标、趋势图占位区、筛选栏和表格区域。测试输出：{"revenue":125000,"orders":842,"conversionRate":"3.8%","topChannels":["Ads","SEO","Email"]}

预期产出

一个销售仪表盘样式的小组件 HTML，可清晰展示核心指标与分析区域

为任务工具生成看板视图

输入

请根据以下任务工具输出，生成一个自包含 HTML 的 MCP App 界面。要求：看板布局，分为待办、进行中、已完成三列，支持任务优先级颜色标签，整体简洁专业。测试输出：{"todo":[{"title":"设计首页","priority":"high"}],"doing":[{"title":"编写接口文档","priority":"medium"}],"done":[{"title":"创建项目仓库","priority":"low"}]}

预期产出

一个任务看板式 HTML 小组件，按状态分栏展示任务并突出优先级

// 文档

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:

MCP Apps API and technical patterns: mcp-apps-reference.md
Visual design defaults and theme tokens: design-guidelines.md

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;

…

查看完整文档 ↗