Context Figma MCP
Related Servers
Alternatives to Context Figma MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnhanced Figma MCP Server that exposes prototype flow data — screen lists, prototype connections, and full flow maps — via the Figma REST API. Designed as a replacement for the official Figma MCP server, adding prototype interaction layer so Claude Code can understand entire user flows from a single Figma URL.715 npm3MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server that wraps the Figma REST API, providing tools like get file metadata, list frames, and export node image URLs for AI SDLC agents.-
- AlicenseAqualityCmaintenanceA local MCP server that reads and edits a Figma Design file through a development plugin, creating real editable layers (frames, text, shapes, components, images) rather than flattened screenshots. It runs entirely on loopback with no personal access token, API key, or cloud bridge, letting an agent inspect documents, build and update layers, export previews, and wire up prototype navigation.10214 npm1MIT
- AlicenseAqualityAmaintenanceProvides read-only Figma design data to AI agents via MCP, supporting local .fig files and browser-based figma.com access without plugins or API tokens.1858 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to read, analyze, and modify Figma designs, including comment management via Figma's REST API. Works with any Figma account and supports parallel execution.807 npmMIT
- AlicenseNot gradedqualityDmaintenanceRead-only Figma MCP server that enables design-to-code workflows by talking to the Figma REST API with a personal access token, for use with Claude Code and GitHub Copilot.3,436 npmMIT
TDQS
Scored across 3 tools
The three tools target distinct granularities: single screen, flow starting points, and global graph. However, get_screen_interactions and get_prototype_graph (when limited to a screen) can both return screen-level interactions, creating minor overlap that descriptions mostly resolve.
All tools use the get_ prefix followed by a snake_case noun phrase (get_screen_interactions, get_prototype_flows, get_prototype_graph), a consistent verb_noun pattern throughout.
Three tools is well-scoped for a focused, read-only prototype-context server. Each tool covers a distinct retrieval need (per-screen details, flow list, navigation graph) without redundancy.
The set covers screen interactions, flow origins, and the full navigation graph, which is complete for read-only prototype context. A minor gap exists for retrieving interactions of arbitrary nodes not tied to a screen or flow, but core workflows are covered.