op-product-design-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OP_PROTOTYPE_OUT | No | 覆盖工作区根目录。 | |
| OP_PROTOTYPE_ROOT | No | 覆盖包根（一般不用）。 | |
| OP_PROTOTYPE_SKIP_SKILL_INSTALL | No | 设置为 1 可关闭 MCP 启动时自动注入 Skill。 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_briefA | 返回强制工作流、SKILL.md 全文和 visual 规则摘要。生成或修改原型前必须先调用。 |
| create_prototypeA | 按 Skill 创建 out//preview.html，内联 CSS，校验硬规则，启动预览并返回内置浏览器 URL。html 省略时用模板脚手架。 |
| update_prototypeA | 覆盖已有原型 HTML。校验通过后写入并通知已打开的预览页 reload。 |
| get_prototypeC | 修改前读取 out//preview.html，基于当前稿增量改，不要每次从空白重写。 |
| start_previewB | 启动 127.0.0.1 热更新 HTTP 服务，返回给 Codex 内置浏览器打开的 URL。 |
| list_prototypesB | 列出 out/ 下已生成的原型及预览 URL。 |
| validate_prototypeA | 按 Skill 硬规则静态检查 HTML 或已有 slug，不写盘。 |
| export_prototypeA | 把已生成的原型导出为可转发的单文件 HTML：CSS 内联、去掉热更新脚本。写入 out//.html，给开发打开即可，不依赖 MCP 预览服务。 |
| get_bundled_cssA | 返回 tokens + theme + layout 拼接结果，生成 HTML 时必须按此顺序内联进 style。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SKILL.md | |
| visual.md | |
| preview.html 模板 | |
| 墙管理示例 | |
| tokens.css | |
| theme.css | |
| layout.css |
TDQS
Scored across 9 tools
Most tools have distinct roles: get_brief (mandatory preamble), get_bundled_css (style tokens), validate_prototype (read-only check), export_prototype (single-file output). However create_prototype overlaps with start_preview since it also launches preview and returns a URL, and create/update_prototype boundary is only clarified by the overwrite wording. Boundaries are mostly clear but one pair needs the description to disambiguate.
All nine tools follow a consistent snake_case verb_noun pattern (get_brief, create_prototype, update_prototype, get_prototype, start_preview, list_prototypes, validate_prototype, export_prototype) with only get_bundled_css deviating slightly in noun form. The convention is predictable and uniform.
Nine tools is well-scoped for a prototype authoring workflow, covering fetch/read/create/update/validate/preview/export/list with no redundant filler. Each tool earns its place in the lifecycle.
The surface covers the core lifecycle (read brief, get/read prototype, create, update, validate, preview, export, list) with no dead ends for the main flow. Minor gaps: no delete_prototype to remove stale drafts and no explicit preview-stop, but these are workable around.