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.
Skills that teach the AI this kind of work; they work alongside this one
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
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 18/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Mokido. Follow https://mcp.popnx.com/i/kolganovr-mokido.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Mokido for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "mokido": { "command": "npx", "args": [ "-y", "mokido" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Mokido tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"mokido": {
"command": "npx",
"args": [
"-y",
"mokido"
]
}
}
}Use Mokido and tell me what you can do for me, then show me one thing✓ If Claude says it is using Mokido or shows a Mokido tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Mokido yet
Mokido runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Mokido
B · Others in Design, images & audio that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Mokido for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user mokido -- npx -y mokido 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Mokido tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user mokido -- npx -y mokidoYou should see Mokido listed as connected
Use Mokido and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Mokido or shows a Mokido tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Mokido for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "mokido": { "command": "npx", "args": [ "-y", "mokido" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Mokido tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Mokido and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Mokido or shows a Mokido tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Mokido for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "mokido": { "type": "stdio", "command": "npx", "args": [ "-y", "mokido" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Mokido tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Mokido and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Mokido or shows a Mokido tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
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"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: mokidoBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account kolganovr, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for mokido@4.4.0
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/kolganovr-mokido)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (4.4.0) reached the registry 22 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| This one Mokido | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | Yes | No |
| Basic checks | 3/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| License | MIT | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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