YetAnotherFigmaMCP
Related Servers
Alternatives to YetAnotherFigmaMCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA local, high-performance replacement for the hosted Figma MCP server that caches Figma files and exposes a local MCP endpoint for Cursor or any MCP client.-
- AlicenseBqualityBmaintenanceLocal MCP server connecting AI clients to the Figma desktop app for inspecting and editing Figma documents via the Plugin API.1630 npm1MIT
- FlicenseBqualityCmaintenanceMCP server that fetches Figma data (file trees, nodes, images, components, styles, variables) and serves as a foundation for Flutter code generation.13-
- FlicenseNot gradedqualityDmaintenanceMCP server for the Figma API. Lets AI agents fetch designs, nodes, and rendered images from Figma.1,589 npm-
- AlicenseAqualityDmaintenanceLocal-first MCP server that connects AI coding agents to the currently open Figma file through a local plugin bridge, requiring no Figma API token.8MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that connects AI clients to Figma via a WebSocket bridge and native plugin, enabling deterministic design operations like inspection, creation, mutation, styling, validation, and optimization.11 npm1MIT
TDQS
Scored across 5 tools
Tools are mostly distinct, but list_figma_frames and get_cached_figma_file both return frame lists, which could cause confusion. Search nodes by name and search frames by title also overlap, though descriptions clarify the scope difference.
All tools follow a consistent <verb>_figma_<resource> pattern, using get for single resources, search/list for plural collections, and qualifiers like by_name or by_title for searches. This makes the set predictable and easy to navigate.
Five tools is a well-scoped size for a read-only Figma caching server, covering file metadata, frame enumeration, node search, and node detail retrieval without unnecessary bloat.
The toolkit covers the core exploration workflow: get file → list frames → search nodes → get node details. Minor gaps exist, such as no direct asset export or style querying, but the stated purpose is served without dead ends.