Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Mokido

by kolganovrversion 4.4.0i★ 2iRuns on your computerRepository ↗
Registry nameio.github.kolganovr/mokido

How to install

What it does

Write to a live Figma canvas, get a screenshot back, and roll back mistakes. Zero deps, free plan.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Design, images & audio

Use together with

Skills that teach the AI this kind of work; they work alongside this one

impeccable

The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.

by pbakaus★ 112,5441 skills

Skill · How-to guide

diagram-design

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.

by cathrynlavery★ 68,0691 skills

Skill · How-to guide

frontend-slides

Create beautiful slides on the web using a coding agent's frontend skills

by zarazhangrui★ 32,5141 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity6/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score18/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

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

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "mokido": {
          "command": "npx",
          "args": [
            "-y",
            "mokido"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    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

What you can do instead

A · Use an app that can connect Mokido

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user mokido -- npx -y mokido
  4. Type /mcp in Claude Code

    You should see Mokido listed as connected

  5. Try it

    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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    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

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Mokido💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user mokido -- npx -y mokido

Claude 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.

At a glance

Downloads per weeki
139/wk
Connection
Runs on your computer
Latest versioni
4.4.0
Published to registryi
Oct 28, 2026
Code last changedi
Nov 17, 2026
Maker
kolganovr
Packages
npm: mokido
Website
github.com
Registry status
Active

Which apps can use it

Based 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

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kolganovr, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for mokido@4.4.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/kolganovr-mokido.svg)](https://mcp.popnx.com/en/servers/kolganovr-mokido)

Discussion

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.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Design, images & audioi

  • More stars than 85% of the other 3275 servers in this category
  • Published to the registry more recently than 59% of the other 3275 servers in this category
  • Basic checks equal to or better than 99% of the other 3275 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Mokido safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed 2 days ago, and the latest version (4.4.0) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server

Similar alternatives

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

HyperFrames by HeyGen

Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.

by heygen-comWidely used★ 86.4K Stars for the whole repoUpdated yesterday

Runs in the cloud✓ heygen.com

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

by pascalorgWidely used↓ 1K/wk★ 25.6K Stars for the whole repoUpdated yesterday

Computer or cloud✓ service owner · pascal.app

draw.io

Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.

by jgraphWidely used★ 5.9KUpdated 2 days ago

Runs in the cloud✓ service owner · draw.ioTried by the PopNx team

Figma MCP Server

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.

by figmaWidely used★ 2.2KUpdated 13 months ago

Runs in the cloud✓ service owner · mcp.figma.com
Compared with similar ones
This one
Mokido
HyperFrames by HeyGenPascal 3D Editordraw.ioFigma MCP ServerRemocn: Remotion MCP server
Runs whereInstalls on your computerRuns in the cloud, nothing to installCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesNoNoYesNo
Basic checks3/34/45/54/44/44/4
LicenseMITApache-2.0MITApache-2.0–MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

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.

⚡ Mokido

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.*


The problem

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.


How it's different

This bridgeFigma Dev Mode MCP (official)FramelinkTalk 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 quotanone — it's local6 / month on Starter seats¹inherits REST rate limitsnone
**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 footprint0 npm deps, npx *or* git clone, Node onlyFigma desktop + paid seatnpx + access tokenBun + 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.


How it works

flowchart LR

subgraph AI ["🤖 Coding Agent"] LLM["Claude Code · Cursor Antigravity · Windsurf"] end

subgraph Bridge ["⚡ MCP Server — Node.js, 0 deps"] Router["Tool Router

  • Job Ledger
  • Target Router"] Opt["Token Optimizer

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.


Quickstart

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:

  1. Plugins → Development → Import plugin from manifest… → pick ~/.mokido/mcp/figma-plugin/manifest.json (the installer prints the full path; the repo's own figma-plugin/ has no bridge token)
  2. Press `Ctrl + Alt + P` (macOS: Cmd + Option + P) to launch Mokido
  3. Status turns green — `CONNECTED`

Restart 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"

or: node install.mjs --token "your_figma_personal_access_token"

Without a token these 7 tools aren't registered at all — see Tool reference.

Updating

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.


What it gives the agent

1. Write freely, then look at the result

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.

2. Undo anything the agent did

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.

3. Read the live canvas for ~700 tokens instead of ~5,000

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.

4. Teach the sandbox new tricks that survive restarts

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");

5. Long jobs that don't die at the timeout

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.

6. Built for the token bill

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*:

DefaultWhy
Screenshotsscale: 1, longest side max_px: 1024, at most 4 images per callimage tokens scale with pixel area (~w·h/750); each image is described as 800x600 ~640tok
capture on insert/mode toolsoffthe auto-lint warnings catch mechanical defects without an image
Text resultscompact 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 limitsome 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

Only the beginning is shown; read the rest in the repo