@mp3wizard/figma-console-mcp 1.14.0 β†’ 1.15.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -8,7 +8,7 @@
8
8
 
9
9
  > **Your design system as an API.** Model Context Protocol server that bridges design and developmentβ€”giving AI assistants complete access to Figma for **extraction**, **creation**, and **debugging**.
10
10
 
11
- > **πŸ†• Cross-File Library Components β€” Use Published Design Systems Across Files:** AI assistants can now discover and instantiate components from published shared libraries into your working file. Search your design system by URL, browse components with full variant detail, and place them β€” no manual copy-paste needed. [See changelog β†’](CHANGELOG.md)
11
+ > **πŸ†• Import Once, Update Never β€” Plugin Bootloader Architecture:** The Desktop Bridge plugin now dynamically loads its UI from the MCP server on every launch. Import the manifest once from `~/.figma-console-mcp/plugin/manifest.json` and you're done forever β€” server updates, new tools, and bug fixes are delivered automatically. Plus: orphaned process cleanup, cross-file library components, and built-in housekeeping. [See changelog β†’](CHANGELOG.md)
12
12
 
13
13
  ## What is this?
14
14
 
@@ -49,9 +49,9 @@ Figma Console MCP connects AI assistants (like Claude) to Figma, enabling:
49
49
  | Real-time monitoring (console, selection) | βœ… | ❌ | ❌ |
50
50
  | Desktop Bridge plugin | βœ… | βœ… | ❌ |
51
51
  | Requires Node.js | Yes | **No** | No |
52
- | **Total tools available** | **59+** | **43** | **22** |
52
+ | **Total tools available** | **63+** | **43** | **22** |
53
53
 
54
- > **Bottom line:** Remote SSE is **read-only** with ~38% of the tools. **Cloud Mode** unlocks write access from web AI clients without Node.js. NPX/Local Git gives the full 60+ tools with real-time monitoring.
54
+ > **Bottom line:** Remote SSE is **read-only** with ~38% of the tools. **Cloud Mode** unlocks write access from web AI clients without Node.js. NPX/Local Git gives the full 63+ tools with real-time monitoring.
55
55
 
56
56
  ---
57
57
 
@@ -59,7 +59,7 @@ Figma Console MCP connects AI assistants (like Claude) to Figma, enabling:
59
59
 
60
60
  **Best for:** Designers who want full AI-assisted design capabilities.
61
61
 
62
- **What you get:** All 60+ tools including design creation, variable management, and component instantiation.
62
+ **What you get:** All 63+ tools including design creation, variable management, and component instantiation.
63
63
 
64
64
  #### Prerequisites
65
65
 
@@ -122,11 +122,12 @@ If you're not sure where to put the JSON configuration above, here's where each
122
122
  **Desktop Bridge Plugin:**
123
123
  1. Open Figma Desktop normally (no special flags needed)
124
124
  2. Go to **Plugins β†’ Development β†’ Import plugin from manifest...**
125
- 3. Select `figma-desktop-bridge/manifest.json` from the figma-console-mcp directory
126
- - **NPX users:** Run `npx figma-console-mcp@latest --print-path` to find the directory
127
- 4. Run the plugin in your Figma file β€” it auto-connects via WebSocket (scans ports 9223–9232)
125
+ 3. Select `~/.figma-console-mcp/plugin/manifest.json` (stable path, auto-created by the MCP server)
126
+ 4. Run the plugin in your Figma file β€” the bootloader finds the MCP server and loads the latest UI automatically
127
+
128
+ > One-time setup. The plugin uses a bootloader that dynamically loads fresh code from the MCP server β€” no need to re-import when the server updates.
128
129
 
129
- > One-time setup. The plugin persists in your Development plugins list across sessions.
130
+ > **Upgrading from v1.14 or earlier?** Your existing plugin still works, but to get the bootloader benefits (no more re-importing), do one final re-import from `~/.figma-console-mcp/plugin/manifest.json`. The path is created automatically when the MCP server starts. Run `npx figma-console-mcp@latest --print-path` to see it. After this one-time upgrade, you're done forever.
130
131
 
131
132
  #### Step 4: Restart Your MCP Client
132
133
 
@@ -152,7 +153,7 @@ Create a simple frame with a blue background
152
153
 
153
154
  **Best for:** Developers who want to modify source code or contribute to the project.
154
155
 
155
- **What you get:** Same 60+ tools as NPX, plus full source code access.
156
+ **What you get:** Same 63+ tools as NPX, plus full source code access.
156
157
 
157
158
  #### Quick Setup
158
159
 
@@ -193,7 +194,7 @@ Then follow [NPX Steps 3-5](#step-3-connect-to-figma-desktop) above.
193
194
 
194
195
  **Best for:** Quickly evaluating the tool or read-only design data extraction.
195
196
 
196
- **What you get:** 22 read-only tools β€” view data, take screenshots, read logs, design-code parity. **Cannot create or modify designs.**
197
+ **What you get:** 9 read-only tools β€” view data, take screenshots, read logs, design-code parity. **Cannot create or modify designs.**
197
198
 
198
199
  #### Claude Desktop (UI Method)
199
200
 
@@ -241,7 +242,7 @@ Ready for design creation? Follow the [NPX Setup](#-npx-setup-recommended) guide
241
242
 
242
243
  **Best for:** Using Claude.ai, v0, Replit, or Lovable to create and modify Figma designs β€” no Node.js required.
243
244
 
244
- **What you get:** 43 tools including full write access β€” design creation, variable management, component instantiation, and all REST API tools. Only real-time monitoring (console logs, selection tracking, document changes) requires Local Mode.
245
+ **What you get:** 52 tools including full write access β€” design creation, variable management, component instantiation, and all REST API tools. Only real-time monitoring (console logs, selection tracking, document changes) requires Local Mode.
245
246
 
246
247
  #### Prerequisites
247
248
 
@@ -298,7 +299,7 @@ AI Client β†’ Cloud MCP Server β†’ Durable Object Relay β†’ Desktop Bridge Plugi
298
299
  | Feature | NPX (Recommended) | Cloud Mode | Local Git | Remote SSE |
299
300
  |---------|-------------------|------------|-----------|------------|
300
301
  | **Setup time** | ~10 minutes | ~5 minutes | ~15 minutes | ~2 minutes |
301
- | **Total tools** | **59+** | **43** | **59+** | **22** (read-only) |
302
+ | **Total tools** | **63+** | **43** | **63+** | **22** (read-only) |
302
303
  | **Design creation** | βœ… | βœ… | βœ… | ❌ |
303
304
  | **Variable management** | βœ… | βœ… | βœ… | ❌ |
304
305
  | **Component instantiation** | βœ… | βœ… | βœ… | ❌ |
@@ -312,7 +313,7 @@ AI Client β†’ Cloud MCP Server β†’ Durable Object Relay β†’ Desktop Bridge Plugi
312
313
  | **Automatic updates** | βœ… (`@latest`) | βœ… | Manual (`git pull`) | βœ… |
313
314
  | **Source code access** | ❌ | ❌ | βœ… | ❌ |
314
315
 
315
- > **Key insight:** Remote SSE is read-only. Cloud Mode adds write access for web AI clients without Node.js. NPX/Local Git give the full 60+ tools.
316
+ > **Key insight:** Remote SSE is read-only. Cloud Mode adds write access for web AI clients without Node.js. NPX/Local Git give the full 63+ tools.
316
317
 
317
318
  **πŸ“– [Complete Feature Comparison](docs/mode-comparison.md)**
318
319
 
@@ -597,7 +598,7 @@ The **Figma Desktop Bridge** plugin is the recommended way to connect Figma to t
597
598
  - The MCP server communicates via **WebSocket** through the Desktop Bridge plugin
598
599
  - The server tries port 9223 first, then automatically falls back through ports 9224–9232 if needed
599
600
  - The plugin scans all ports in the range and connects to every active server it finds
600
- - All 60+ tools work through the WebSocket transport
601
+ - All 63+ tools work through the WebSocket transport
601
602
 
602
603
  **Multiple files:** The WebSocket server supports multiple simultaneous plugin connections β€” one per open Figma file. Each connection is tracked by file key with independent state (selection, document changes, console logs).
603
604
 
@@ -637,11 +638,11 @@ When two processes tried to start the MCP server (e.g., Claude Desktop's Chat ta
637
638
 
638
639
  ### Do I Need to Do Anything?
639
640
 
640
- **If you're running a single instance:** Nothing changes. You'll still use port 9223 as before.
641
-
642
- **If you want multi-instance:** Re-import the Desktop Bridge plugin in Figma (Plugins β†’ Development β†’ Import plugin from manifest). This updates the plugin to scan all ports and connect to every active server.
643
-
644
- > **Note:** The server-side update happens automatically when you update the npm package. Only the plugin needs a one-time re-import to enable multi-connection support.
641
+ **Nothing.** Multi-instance support is fully automatic:
642
+ - Each MCP server claims the next available port in the range
643
+ - The bootloader plugin scans all ports and connects to every active server
644
+ - Orphaned processes from closed tabs are automatically cleaned up on startup
645
+ - No re-importing, no manual port management
645
646
 
646
647
  ---
647
648
 
@@ -733,7 +734,7 @@ The architecture supports adding new apps with minimal boilerplate β€” each app
733
734
 
734
735
  ## πŸ›€οΈ Roadmap
735
736
 
736
- **Current Status:** v1.12.0 (Stable) - Production-ready with Cloud Write Relay, Design System Kit, WebSocket-only connectivity, smart multi-file tracking, 60+ tools, Comments API, and MCP Apps
737
+ **Current Status:** v1.12.0 (Stable) - Production-ready with Cloud Write Relay, Design System Kit, WebSocket-only connectivity, smart multi-file tracking, 63+ tools, Comments API, and MCP Apps
737
738
 
738
739
  **Recent Releases:**
739
740
  - [x] **v1.12.0** - Cloud Write Relay: web AI clients (Claude.ai, v0, Replit, Lovable) can create and modify Figma designs via cloud relay pairing β€” no Node.js required