impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Write to a live Figma canvas, get a screenshot back, and roll back mistakes. Zero deps, free plan.
教 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)排序,由以下部分组成
| 热度 | 6/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 18/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Mokido。按照 https://mcp.popnx.com/i/kolganovr-mokido.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Mokido,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "mokido": { "command": "npx", "args": [ "-y", "mokido" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Mokido 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"mokido": {
"command": "npx",
"args": [
"-y",
"mokido"
]
}
}
}用 Mokido 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Mokido,或回答中出现 Mokido 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Mokido
Mokido 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Mokido 的应用
B · 设计、图片与音频 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Mokido,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user mokido -- npx -y mokido 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Mokido 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user mokido -- npx -y mokido应能看到 Mokido 在列表中并显示已连接
用 Mokido 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Mokido,或回答中出现 Mokido 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Mokido,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "mokido": { "command": "npx", "args": [ "-y", "mokido" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Mokido 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Mokido 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Mokido,或回答中出现 Mokido 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Mokido,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "mokido": { "type": "stdio", "command": "npx", "args": [ "-y", "mokido" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Mokido 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Mokido 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Mokido,或回答中出现 Mokido 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user mokido -- npx -y mokidoClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"mokido": {
"command": "npx",
"args": [
"-y",
"mokido"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mokido": {
"command": "npx",
"args": [
"-y",
"mokido"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"mokido": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mokido"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 kolganovr 验证,该账户拥有此仓库
代码最后更新于前天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 mokido@4.4.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/kolganovr-mokido)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(4.4.0)于22天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有: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.
| 本项 Mokido | 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、图片和脚本已被移除。链接会离开本站。
MCP server for Figma design. Let an AI agent design in Figma — and actually see what it drew.
Formerly figma-mcp-bridge (@kolganovr/figma-mcp-bridge on npm). Old links redirect here.
A zero-dependency MCP server that gives coding agents read *and write* access to a live Figma canvas, then closes the loop by handing the rendered PNG back to the model for visual self-critique.
*One prompt, two screens: the agent reads your design system, builds them live in the file you have open, checks its own screenshot and fixes the layout. 56 seconds of real time, sped up.*
Coding agents are effectively blind inside Figma. Most Figma MCP servers are read-only — they flatten a design into text so a model can turn it into code, and the traffic stops there. The ones that *can* write are either gated behind a paid Figma seat with a monthly tool-call quota, or expose a fixed vocabulary of commands (create_rectangle, set_fill) that runs out the moment the task gets specific.
And none of them answer the question that actually matters after a write: did it look right? An agent that draws a card, gets back {"ok": true}, and moves on has no way to notice that its text overflowed, its contrast failed, or its frame landed on top of someone else's work.
This bridge closes that loop, and adds the safety rails an autonomous agent needs to be trusted with a real design file.
| This bridge | Figma Dev Mode MCP (official) | Framelink | Talk to Figma | |
|---|---|---|---|---|
| Writes to the canvas | ✅ arbitrary JS in the sandbox | ✅ code-to-canvas | ❌ read-only | ✅ fixed command set |
| Visual feedback loop | ✅ auto-framed PNG on any write (capture: true) | ⚠️ separate screenshot call | ❌ | ❌ |
| Undo the agent's work | ✅ figma_rollback | ❌ | n/a | ❌ |
| Works on the Figma Free plan | ✅ | ❌ Dev/Full seat, paid plan¹ | ✅ | ✅ |
| Tool-call quota | none — it's local | 6 / month on Starter seats¹ | inherits REST rate limits | none |
| **Token-optimized read of the *live* doc** | ✅ 86–91% smaller² | ⚠️ partial | ❌ REST only | ❌ |
| Persistent code modules in-sandbox | ✅ bridge.define/require | ❌ | ❌ | ❌ |
| Long jobs survive their own timeout | ✅ async job_id, one blocking wait | ❌ | n/a | ❌ |
| Token budget per call | ✅ capped text, sized images, compact JSON | ❌ | ⚠️ read-side only | ❌ |
| Install footprint | 0 npm deps, npx *or* git clone, Node only | Figma desktop + paid seat | npx + access token | Bun + a second server process |
The short version: Framelink is the best choice if you only want to turn an existing design into code. The official server is the safest choice if you're already on a paid Figma plan and want Code Connect. This bridge is for the case where the agent is doing the designing — where it needs to write freely, check its own work, and be undoable when it gets it wrong.
flowchart LR
subgraph AI ["🤖 Coding Agent"] LLM["Claude Code · Cursor Antigravity · Windsurf"] end
subgraph Bridge ["⚡ MCP Server — Node.js, 0 deps"] Router["Tool Router
REST + LIVE"] end
subgraph Figma ["🎨 Figma Desktop"] Plugin["Bridge Plugin Checkpoint Journal Component Index"] Canvas["Live Canvas"] end
LLM -->|"stdio JSON-RPC"| Router Router <-->|"WebSocket :8765"| Plugin Plugin -->|"execute in sandbox"| Canvas Canvas -->|"export PNG"| Plugin Plugin -->|"raw node tree"| Opt Opt -.->|"86% smaller"| LLM Plugin ==>|"screenshot + warnings"| LLM
The agent speaks plain MCP over stdio. The server owns a hand-rolled RFC 6455 WebSocket on :8765, which the Figma plugin connects to — so commands reach the canvas with no polling latency, and results (including multi-megabyte base64 PNGs) stream straight back.
npx mokido
Or, to read the installer before it touches your machine — it's the same script either way, just fetched differently:
git clone https://github.com/kolganovr/mokido.git
cd mokido node install.mjs
Both copy the server and plugin into place and register the MCP server in every AI client config they find — Claude Desktop, Claude Code, Cursor, Windsurf, Antigravity. The npm package exists purely for a shorter first command; it doesn't add a single runtime dependency — dependencies is empty in its package.json too, and no Python is needed either. node is the only runtime this project ever needs, for the installer and the server alike.
Then, in Figma Desktop:
~/.mokido/mcp/figma-plugin/manifest.json (the installer prints the full path; the repo's own figma-plugin/ has no bridge token)Cmd + Option + P) to launch MokidoRestart your AI client so it picks up the new tools. Verify anytime with:
npx mokido --doctor # or: node install.mjs --doctor
Optional: Figma Cloud REST access
The live canvas tools need no token. If you also want to read *unopened* cloud files (get_file, get_node, get_styles, …), supply a personal access token:
npx mokido --token "your_figma_personal_access_token"
Without a token these 7 tools aren't registered at all — see Tool reference.
Updating is the same installer run again. It overwrites the copy in ~/.mokido/mcp, keeps your bridge token and client configs, and removes copies left by older versions.
npx mokido@latest --update
Keep @latest: a bare npx mokido can reuse the version npx cached last time. From a clone:
git pull
node install.mjs --update
Then reopen the plugin in Figma (Ctrl + Alt + P) and restart your AI client. A server that was already running keeps the old code in memory, and the plugin shows "Update needed" until it restarts.
You don't have to watch for releases: once a day the server checks npm and prints a one-line notice to your client's MCP log when a newer version is out (see the update check). What changed in each version is in CHANGELOG.md.
Agents updating it for you follow the same steps in AGENTS.md.
capture: true returns a PNG of exactly what the call just created or modified — auto-framed to the changed nodes, never the whole page, and *never* by hijacking the user's selection.
// agent calls figma_execute_code
{ "code": "const f = figma.createFrame(); /* ... */ return f.id;", "capture": true }
// agent gets back — text + image in one response { "ok": true, "created": ["12:34"], "warnings": ["Text \"Total\" has ~3.1:1 contrast against its parent fill (WCAG AA wants 4.5:1)."], "checkpoint_id": "cp_mfk3p2a_7", "duration_ms": 840 }
The warnings array is a cheap auto-lint over the touched subtree — text overflow, low contrast, zero-size nodes. It catches the obvious mistakes without spending a screenshot round trip.
Every write opens a checkpoint automatically. One call reverses it — no Ctrl+Z rolling back over the human's own unrelated work.
// agent calls figma_rollback
{ "checkpoint_id": "last" }
// gets back { "ok": true, "checkpoint_id": "cp_mfk3p2a_7", "label": "Generate checkout flow", "removed": ["12:34", "12:35"], // nodes the call created — deleted "restored": ["9:11"], // nodes it modified — properties put back "missing": [] // ids that no longer exist }
Created nodes are tracked automatically via a Proxy around figma.create*(). Property edits are tracked when snapshotted. Deletions are honestly reported as unrecoverable rather than silently lost.
The same pruning + Pseudo-JSX pipeline that powers the cloud tools, pointed at whatever is open right now. Measured on a realistic 6-card layout: 20 KB of raw API JSON → 2.7 KB (86% smaller).
<Frame id="1:1" name="Landing" w="1440" h="900" row gap="20">
Feature 0
budget_tokens caps the response: if the requested depth overshoots, the server re-serializes the already-fetched tree shallower — no second round trip — and appends a comment saying what it did and which id to fetch for more.
Every figma_execute_code call is a fresh function scope, so helpers normally die instantly. bridge.define compiles and stores a module *inside the .fig document*:
// once
bridge.define("kit", async function label(parent, text) { /* ... */ } module.exports = { label }; );
// in any later call — including next week, after a Figma restart const { label } = bridge.require("kit");
A generation still running after 45s hands back a job_id instead of failing while the plugin keeps working. figma_job_status then blocks until the job finishes (up to wait_ms, 45s by default) — one call, not a polling loop. Progress from progress(step, of, note) is included while it runs; a job silent for 2 minutes is flagged stalled, and one whose plugin disconnected fails at once with PLUGIN_DISCONNECTED instead of running out the clock. A call that times out behind a still-running job says so (PLUGIN_BUSY, naming the job) instead of inviting a blind retry.
In an agent loop a tool call is paid for twice: once when it returns, and again on every later turn, because its output stays in the context that each turn re-reads. So the bridge optimizes for *fewer turns* and *smaller residue*:
| Default | Why | |
|---|---|---|
| Screenshots | scale: 1, longest side max_px: 1024, at most 4 images per call | image tokens scale with pixel area (~w·h/750); each image is described as 800x600 ~640tok |
capture on insert/mode tools | off | the auto-lint warnings catch mechanical defects without an image |
| Text results | compact JSON; every response is kept under max_output_bytes (3500 UTF-8 bytes, whole envelope) by structural shrinking; a requested value above the 3900-byte ceiling is capped to it, 0 = no limit | some clients (Antigravity) spill output over ~4 KB into a file the model must open with an extra call; the full value stays in bridge.state.lastResult |
| Che