Mokido
Related Servers
Alternatives to Mokido
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables a locally run agent or script to read and write a real Figma layer tree through a local bridge — inspecting node structure and variables, exporting screenshots into the model's context, and performing batched create/update/move/rename/delete operations that collapse into a single undo step. All traffic stays on localhost between the bridge and the Figma plugin, with design-token auditing, binding, and creation included.1 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to read a Figma design and render a new one back through the Figma Plugin API using a single shared tree format, so designs can be inspected and built without a REST token or per-month call limit. Exposes tools for rendering whole screens, patching layers, finding and selecting nodes, managing pages, tokens and variables, capturing screenshots, exporting assets, and running Plugin API code.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to read and modify the user's currently open Figma file by executing JavaScript in Figma's sandbox, all through a local bridge with status monitoring, node jumping, and automatic rollback on errors.1MIT
- AlicenseNot gradedqualityBmaintenanceFast, quota-free Figma automation for coding agents, enabling AI agents to read, edit, migrate, audit, screenshot, and prototype inside Figma Desktop files.9MIT

Screenbookofficial
AlicenseNot gradedqualityCmaintenanceEnables an AI agent to read and write a product's design screens on a shared, versioned canvas: creating and editing HTML screens and shared parts, taking screenshots, linking flows, posting comments and annotations, and opening or approving proposals. Every drawing is returned with its screenshot so the agent can see what it produced, letting screens persist and evolve across chats instead of starting from zero.1MIT- AlicenseAqualityBmaintenanceEnables AI agents to read and draw on Figma canvas safely, with built-in safeguards for layout, overlays, and verification.5104MIT
TDQS
Scored across 14 tools
Write-side tools are fairly distinct, but the read surface has several overlapping options: figma_inspect, figma_read_canvas, figma_get_selection, figma_get_canvas_layout, and figma_find_components all retrieve live document information. Descriptions give guidance, but an agent may still struggle to choose between figma_inspect and figma_read_canvas for general document reading.
All tools use a consistent figma_ snake_case prefix, and most follow a verb_noun pattern (get_selection, find_components, insert_svg, set_variables_mode). Minor deviations exist in noun-style names like figma_screenshot and figma_job_status, and verb-only names like figma_inspect and figma_rollback.
At 14 tools, the set is within the ideal range and each tool has a recognizable role in the Figma bridge workflow. The count is well-scoped despite some tools being very broad.
The surface covers reading, writing, undo, async job handling, screenshots, component insertion, SVG insertion, selection inspection, and variables mode switching. Minor gaps remain around creating/editing Figma Variables and cloud/API document tools, but figma_execute_code can cover many custom write operations.