"How to use Figma" matching MCP servers:

MCP server for downloading images from Figma designs using access tokens. Supports multiple export formats and scale factors via a single tool.

Enables an agent to read, edit, and build Figma designs from scratch — including style guides, variables, components, and screens — through a local plugin bridge to the open file's Plugin API, with no Figma token or REST API calls.

Enables extraction of design context from Figma files as CSS-like properties and provides tools to render Figma nodes as images. It integrates with AI agents via the Model Context Protocol to facilitate design-to-code workflows by providing layout, style, and typography information.

Enables interaction with Figma designs through the Figma API, allowing users to export images in multiple formats, extract style data and CSS, analyze design elements, and retrieve SVG code from Figma files. Supports batch operations and comprehensive design element analysis including images, vectors, and components.

A comprehensive MCP server for Vue component development and Figma design restoration, featuring snapDOM-powered screenshots, pixel-perfect visual comparison, and automated SVG optimization.

Local MCP server for Gateway-managed computer use that exposes computer.* tools with desktop control, OCR, and user-visible safety overlays.

MCP server for ingesting UI screenshots, Figma MCP node JSON, or hybrid Figma-plus-screenshot sources into a cross-platform design-to-code artifact pipeline.

MCP server for controlling Figma Slides — create, edit, and screenshot slides from any AI assistant that supports MCP.

Enables a locally run agent or script to read and write a real Figma layer tree through a local bridge — inspecting node structure and variables, exporting screenshots into the model's context, and performing batched create/update/move/rename/delete operations that collapse into a single undo step. All traffic stays on localhost between the bridge and the Figma plugin, with design-token auditing, binding, and creation included.

Enables stdio MCP clients such as Cursor and Claude Code to read and modify the currently open Figma Desktop file, export selected nodes as local PNG/SVG files, and create or edit basic canvas nodes using precise layout data for pixel-level reconstruction.

Writes to a live Figma canvas via arbitrary sandboxed JS, returns an auto-framed screenshot in the same call for visual self-checks, and opens a checkpoint on every write so an agent's mistake can be rolled back without touching the human's own edits. Zero npm dependencies, works on the Figma free plan — no paid Dev Mode seat or tool-call quota.

Enables AI coding tools such as Claude Code and Codex to interact with and modify Figma designs via the Model Context Protocol.

Uploads temporary Figma MCP asset URLs to the CDN after Tinify optimization.

MCP server for the Figma API. Lets AI agents fetch designs, nodes, and rendered images from Figma.

An MCP server that bridges Claude Code to Figma, enabling AI-driven design creation, modification, and export via semantic tools and WebSocket communication.

An MCP server that enables AI agents to search, retrieve, and curate free stock photos and videos from Pexels, with tools, resources, and prompts for easy integration.

An MCP server enabling agents to generate videos via the vidhook render API, with tools to validate movie definitions, start renders, and check status.

Enables drawing commands to be rendered into raster images, supporting shapes like lines, rectangles, circles, ellipses, and triangles, with results returned as inline PNGs or saved to files.

Render HTML/CSS to PNG/JPG/WebP directly from Claude Desktop, Claude Code, Cursor, or any MCP-compatible client.

Enables AI assistants to generate real images via multiple models (OpenAI, Gemini, Recraft, Seedream, Grok, Arrow) and returns usable file paths instead of base64 data.