figma
Related Servers
Alternatives to figma
No user-submitted related servers found.
Related Servers
- 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.2,146 npmMIT
- 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.716 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that bridges Claude to Figma, enabling read access via REST and full create/edit capabilities through the Figma Plugin API over a local WebSocket.23 npmMIT
- AlicenseNot gradedqualityBmaintenanceLocal MCP server exposing Figma REST API tools to AI agents, enabling file reads, comments, variables, and other resource operations. Works with personal access tokens and integrates with Claude, Cursor, Codex, and more.MIT
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol (MCP) server that enables Claude to create and manipulate designs in Figma through either a Figma plugin or directly via the Figma API.-
- FlicenseNot gradedqualityDmaintenanceCustom MCP server for the Figma REST API that enables inspecting file structures, nodes, styles, components, variables, and exporting images, with optional comment posting. It is read-only except for posting comments and is designed for use with Claude Code.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct role in a design-to-code pipeline: list frames, extract layout, extract tokens, export icons, and render a preview. The descriptions explicitly sequence them, with list_frames as the entry point and frame id passed to the others.
All names follow a consistent verb_noun snake_case pattern: list_frames, get_layout, get_tokens, export_icons, render_frame. The convention is predictable and easy to scan.
Five tools is well-scoped for a focused Figma extraction server. Each tool earns its place by covering a distinct artifact needed to build a page from a design.
The surface covers the core workflow: discover frames, inspect layout, get design tokens, export icons, and visually compare via render. Minor gaps exist for other asset types or broader file-level operations, but the main build path is complete.