impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
MCP server for document-ready UML diagrams: the AI lays them out, cysUML draws and checks them.
作者提供的原文
教 AI 做这类工作的 Skill,可与本项一起使用
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 cysUML。按照 https://mcp.popnx.com/i/yschoi9733-cysuml.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server cysUML,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "cysuml": { "command": "uvx", "args": [ "cysuml" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 cysUML 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"cysuml": {
"command": "uvx",
"args": [
"cysuml"
]
}
}
}用 cysUML 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 cysUML,或回答中出现 cysUML 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 cysUML
cysUML 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 cysUML 的应用
B · 设计、图片与音频 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server cysUML,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user cysuml -- uvx cysuml 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 cysUML 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user cysuml -- uvx cysuml应能看到 cysUML 在列表中并显示已连接
用 cysUML 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 cysUML,或回答中出现 cysUML 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server cysUML,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "cysuml": { "command": "uvx", "args": [ "cysuml" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 cysUML 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 cysUML 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 cysUML,或回答中出现 cysUML 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server cysUML,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "cysuml": { "type": "stdio", "command": "uvx", "args": [ "cysuml" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 cysUML 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 cysUML 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 cysUML,或回答中出现 cysUML 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user cysuml -- uvx cysumlClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"cysuml": {
"command": "uvx",
"args": [
"cysuml"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"cysuml": {
"command": "uvx",
"args": [
"cysuml"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"cysuml": {
"type": "stdio",
"command": "uvx",
"args": [
"cysuml"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 yschoi9733 验证,该账户拥有此仓库
代码最后更新于今天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 cysuml@0.2.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月18日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/yschoi9733-cysuml)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于今天,最新版本(0.2.1)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
The Figma MCP server brings Figma design context directly into your AI workflow.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| 本项 cysUML | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server for document-ready UML diagrams: the AI lays them out, cysUML draws and checks them.
한국어 안내
Auto-layout tools keep boxes apart, but they decide where everything goes: it is hard to get the arrangement you want, one more class can reshuffle the whole picture, and labels can still crowd the lines. cysUML takes the other way round: your AI assistant decides where every box goes, cysUML draws exactly that and checks the drawing. An assistant placing boxes itself can get it wrong, so if boxes overlap, a line runs through a box or a label, or labels overlap, the check fails and says what to move. The assistant fixes the layout and draws again until the check passes.
For example, here the assistant first put Product right under OrderLine, on the line from Customer to Payment. The line then passes under the Product box, which hides it, and the picture says something the model doesn't: Product is not related to Customer or Payment, yet it looks as if pays joined Customer to Product, and as if Product had its own line to Payment. The check fails on exactly this and tells the assistant to move that box or change the line's bend points:
The assistant moved Product to the right of OrderLine, pulled Payment and CardPayment left into the room it left, drew again, and the check passed:
You need uv. This one line downloads cysUML from PyPI and starts the server:
uvx cysuml
It talks MCP over stdin/stdout, so on its own it just waits for a client. Register it with your MCP client instead.
Claude Code
claude mcp add cysuml -- uvx cysuml
Other clients (Claude Desktop, Cursor, …) take the same command in their JSON config:
{
"mcpServers": { "cysuml": { "command": "uvx", "args": ["cysuml"] } } }
Versions. uvx cysuml runs the newest release: each time the client starts the server, uv asks PyPI and reuses the answer for up to ten minutes. If you installed it with uv tool install cysuml, uvx runs that copy instead; update it with uv tool upgrade cysuml. To stay on one version, put it after the name: uvx cysuml@0.2.1 (in JSON, "args": ["cysuml@0.2.1"]). The releases are listed in the release history.
Ask your assistant for a diagram, for example "draw a class diagram of the order domain with cysUML" or "draw the checkout flow as a sequence diagram with cysUML". The server tells the assistant how to lay it out, so you don't have to.
The tool is draw_class_diagram. The assistant sends boxes with their top-left corners and relations with optional bend points:
{
"file_name": "order", "classes": [ {"name": "Order", "left": 0, "top": 0, "attributes": ["-id: long"]}, {"name": "Customer", "left": 200, "top": 0} ], "relations": [ {"kind": "association", "from": "Order", "to": "Customer", "name": "places", "to_multiplicity": "1"} ] }
It gets back the check result, the size and place of every box as drawn, the saved file paths, and the picture. The check fails when boxes overlap, a line runs through a box, a label or another line's arrowhead, or labels overlap. A relation's name is drawn on top of that relation's line, which breaks around the name, so the stretch of line it sits on doesn't count as running through it (the rest of that line, its end shapes and other lines still do). A name with no room on its line (including a line too short to stay visible on both sides of the name), or on a line that loops back to the same box, goes beside the line, and if putting the names on their lines makes the whole picture fail more, every name goes beside its line. Crossing lines and the picture size are reported but don't fail. Inheritance lines from several children to one parent may join into one trunk that shares a single triangle (realization lines too, but not mixed with inheritance); the relations argument description tells the assistant how to give the bend points for it. When both kinds come to one parent, the result lists a point for each kind either side of the point the parent's lines aim at (usually its middle); a line whose last bend point sits right below its kind's point goes straight up to it, so the two triangles sit side by side. A parent too narrow for two triangles (a class drawn narrower than 48px, or in the package, component and deployment tools an icon-style artifact) gets no points.
Relations must follow UML notation, and the tool rejects the input otherwise: a generalization joins two boxes of the same kind (a class and an abstract class count as one kind), never runs in a cycle, and neither a generalization nor a realization points back to its own box. A realization made by an interface, or one that ends on something other than an interface, is drawn and reported as a notice. The package, component and deployment tools follow the same rules. There a package or a provided interface ball is never an end of a generalization, a realization made by either of them gets a notice, and a realization from a class to a component (the class realizes the component) does not. Icon notations of components and artifacts count as the same kind as the plain ones.
The tool is draw_package_diagram. It draws packages and the dependencies between them, with classes and packages inside packages, and takes components, artifacts and nodes in the same picture. Every element has a kind. An element names the one it sits in with in, and the outer element grows right and down to cover it:
{
"file_name": "packages", "elements": [ {"kind": "package", "name": "web", "left": 0, "top": 0}, {"kind": "class", "name": "OrderController", "in": "web", "left": 20, "top": 44}, {"kind": "package", "name": "domain", "left": 0, "top": 180}, {"kind": "class", "name": "Order", "in": "domain", "left": 20, "top": 224}, {"kind": "class", "name": "Customer", "in": "domain", "left": 200, "top": 224} ], "relations": [ {"kind": "dependency", "from": "web", "to": "domain", "stereotype": "use"}, {"kind": "association", "from": "Order", "to": "Customer", "name": "places", "to_multiplicity": "1"} ] }
It gets back the same things as the class diagram tool, with the place of every element (and, for a package, the point its lines aim at, since that is not the middle of the package). Besides the class diagram checks, the check fails when an element inside another sits too close to its edge or name tab, or a line runs along the edge of a package it starts or ends in, or through a package's name tab.
Components and artifacts can also be drawn in icon notation. component_icon is the UML 1 component: a box with two small rectangles across its left edge, which lines may not cross. artifact_icon is a folded-page icon with the name (often a file name) outside it, on the side name_side gives.
The tool is draw_component_diagram. It draws components with the interfaces they provide, the artifacts that implement them, and the classes that realize them. It takes every element of the package diagram tool (icon notations included), plus lollipop: a provided interface drawn as a small circle with its name outside (name_side puts the name below, above, left or right of the circle). The providing component joins the circle with an association, drawn without an arrowhead in this tool unless navigable is given, and each user points at the circle with a dependency:
{
"file_name": "components", "elements": [ {"kind": "package", "name": "web", "left": 0, "top": 0}, {"kind": "component", "name": "OrderController", "in": "web", "left": 20, "top": 44}, {"kind": "component", "name": "AdminController", "in": "web", "left": 220, "top": 44}, {"kind": "package", "name": "service", "left": 0, "top": 220}, {"kind": "component", "name": "OrderService", "in": "service", "left": 110, "top": 324}, {"kind": "lollipop", "name": "OrderApi", "in": "service", "left": 70, "top": 264, "name_side": "left"}, {"kind": "artifact", "name": "order-service.jar", "left": 400, "top": 324} ], "relations": [ {"kind": "association", "from": "OrderService", "to": "OrderApi"}, {"kind": "dependency", "from": "OrderController", "to": "OrderApi"}, {"kind": "dependency", "from": "AdminController", "to": "OrderApi"}, {"kind": "dependency", "from": "order-service.jar", "to": "OrderService", "stereotype": "manifest"} ] }
It gets back the same things as the package diagram tool, and for each circle the place of the circle alone next to the place of the circle with its name. The checks are the same: a line through a circle or its name fails.
A user of an interface can also be drawn as a socket. A requires relation from the user to the circle is a solid line that stops short of the circle and ends in a half circle wrapped around it (ball and socket). Its to must be a lollipop and its from must not be one. A circle takes one socket, since two half circles overlap, so any other user points at the circle with a dependency. A line that touches a half circle fails. With the icon notations, the same tool draws a textbook-style picture of UML 1 components and folded-page artifacts:
{
"file_name": "billing", "elements": [ {"kind": "artifact_icon", "name": "Billing.exe", "left": 38, "top": 0, "name_side": "right"}, {"kind": "component_icon", "name": "Billing", "left": 0, "top": 110}, {"kind": "lollipop", "name": "IBilling", "left": 190, "top": 124}, {"kind": "component_icon", "name": "Register", "stereotype": "component", "left": 320, "top": 103}, {"kind": "component_icon", "name": "Course", "left": 0, "top": 260}, {"kind": "artifact_icon", "name": "Course.dll", "left": 24, "top": 380} ], "relations": [ {"kind": "dependency", "from": "Billing.exe", "to": "Billing", "stereotype": "manifest"}, {"kind": "association", "from": "Billing", "to": "IBilling"}, {"kind": "requires", "from": "Register", "to": "IBilling"}, {"kind": "dependency", "from": "Register", "to": "Course", "via": [[385, 284]]}, {"kind": "dependency", "from": "Course.dll", "to": "Course", "stereotype": "manifest"} ] }
The tool is draw_deployment_diagram. It shows which computers (nodes) the software runs on: components and artifacts sit inside nodes with in, and a node can sit inside another node. It takes the same elements as the package dia