figma-ui-mcp
Related Servers
Alternatives to figma-ui-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to draw UI directly on a Figma Desktop canvas and read existing designs back as structured JSON, tokens, CSS, and screenshots, all over a localhost bridge without external API keys.1,645 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read and write Figma designs through a local WebSocket relay, turning Figma selections into framework-aware code and building/editing designs directly on the canvas. Provides 112 MCP tools for bidirectional design-code workflows with support for any MCP client.MIT
- AlicenseBqualityAmaintenanceA local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.1223 npm1MIT
- AlicenseAqualityBmaintenanceThe Figma desktop app as an MCP server. Gives AI agents the full Figma Plugin API on your open file: read, write, tokens, components, exports, undo. Runs locally with no cloud API, no token and no quota.1047 npm1MIT
- 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
- AlicenseBqualityCmaintenanceLocal MCP server connecting AI clients to the Figma desktop app for inspecting and editing Figma documents via the Plugin API.1623 npm1MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: documentation retrieval, reading design data, generating rule sheets, checking connection status, and executing write operations. The slight overlap between figma_docs and figma_rules is mitigated by their different scopes (general reference vs. file-specific aggregation), so no ambiguity exists.
All tools follow a consistent 'figma_verb' pattern (docs, read, rules, status, write). The verbs are clear and indicative of each tool's function, making the set predictable and easy to understand.
With 5 tools, the server covers the essential operations for Figma interaction (status, read, write, documentation, rule generation) without unnecessary bloat. The count is well-scoped and each tool earns its place.
The tool set covers the primary use cases: reading design data, writing/modifying designs via code, generating design rules, checking connection, and accessing documentation. While the write tool is extremely versatile, dedicated tools for specific operations like deleting or listing components are missing, but the JavaScript execution fills that gap. Minor gaps remain for very specialized tasks.