io.github.workingmodel/figma-vector-mcp
Figma Vector MCP
Is the Figma Vector MCP server down? No. It is up and needs env, probed 2026-11-04.
Let Claude create and edit fully editable vector nodes on the Figma canvas.
needs env probed 2026-11-15 · unchanged since 2026-11-04
MCP error -32000: Connection closed [INFO] Connecting to socket relay at ws://localhost:NaN… [ERROR] Fatal: SyntaxError: Invalid URL: ws://localhost:NaN
- Run it
- npx -y figma-vector-mcp@0.3.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/workingmodel/wm-figma-vector-mcp
- Website
- https://www.workingmodel.co/
- Registry
- active, updated 2026-10-22 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- MindMax io.github.woodpeng/mindmax · alive
- MindMax Write io.github.woodpeng/mindmax-write · alive
- Witness io.github.wookat/witness · alive
- io.github.worakorn-prince/th-memory-mcp · crashed on start
- Woven io.github.woven-video/woven · install failed
- Chestnyi Znak MCP Server io.github.woyaxnini/chestnyi-znak · alive
- io.github.woyaxnini/max-messenger · alive
- Ozon Seller MCP Server io.github.woyaxnini/ozon-seller · alive
Servers that mention vector.
- CleanVector ai.cleanvector/cleanvector · alive
- Contexta cc.contexta/contexta-mcp · needs auth
- Gnosis Memory com.gnosismemory/memory · alive
- stagenth · 二维码工具箱 com.stagenth/qr-kit · TLS error
- Vector Panda com.vectorpanda/database · needs auth
- Vector Panda Documentation com.vectorpanda/docs · alive
- ViewsMeet Pick + Predict com.viewsmeet/participate · alive
- Visual Sandbox com.visualsandbox/visual-sandbox · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.