Connect Figma with AI agents using Model Context Protocol (MCP). Seamlessly integrate Figma tools and actions into Claude, Cursor, Windsurf, and other AI applications for enhanced workflow automation.
Design & Creative Tools tools for AI automation
Install Figma MCP server in minutes. Choose your AI platform: Cursor, Claude Desktop, Windsurf, or use HTTP endpoint for custom integrations. Follow our step-by-step guide to connect Figma with your AI agent.
Explore other MCP integrations: Gmail MCP, Notion MCP, GitHub MCP, Linear MCP, Slack MCP, Google Sheets MCP, and 100+ more AI agent tools.
A collaborative interface design tool.
32870
1801
Design & Creative Tools
Paste and run this command in your terminal to set up Cursor with MCP
After running the command, restart Cursor to start using the MCP Server.
Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.
Posts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.
Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`.
Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.
Manages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and ensure `variablemodevalues` match the target variable's `resolvedtype`.
Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.
Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.
Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.
Deletes a development resource (used to link figma design elements to external developer information like code or tasks) from a specified figma file.
Convert design tokens to tailwind css configuration. takes the output from extractdesigntokens and generates: - tailwind.config.ts/js with theme extensions - optional globals.css with font imports note: shadow colors can be provided in either string format (e.g., "rgba(15, 110, 110, 0.32)") or dictionary format (e.g., {"r": 0.059, "g": 0.431, "b": 0.431, "a": 0.32}).
Detect background layers for selected nodes. uses geometric analysis, z-index ordering, and visual properties to identify potential background layers.
š smart figma resource discovery - never guess ids again! šÆ easiest method: just paste any figma url to get all ids: ⢠file urls: https://www.figma.com/file/abc123/design ā get file key ⢠design urls: https://www.figma.com/design/abc123/design ā get file key ⢠node urls: ...?node-id=123:456 ā get file key + node id ⢠team urls: .../team/123456/... ā get team id š step-by-step discovery: 1. team id ā projects list (with project ids) 2. project id ā files list (with file keys + thumbnails) 3. file key ā nodes list (with node ids + hierarchy) š” common workflows: ⢠extract from url: discoverfigmaresources(figma url="...") ⢠browse team: discoverfigmaresources(team id="123") ⢠list files: discoverfigmaresources(project id="proj 456") ⢠find nodes: discoverfigmaresources(file key="abc123") ⨠get file key for getfilejson, node ids for detectbackground, etc.
Download images from figma file nodes. renders specified nodes as images and downloads them using mercury's filedownloadable infrastructure. supports png, svg, jpg, and pdf formats.
Extract design tokens from figma files. combines styles, variables, and extracted values to create a comprehensive design token system.
Extract prototype interactions and animations from figma files. analyzes the prototype data to extract: - user interactions (clicks, hovers, etc.) - transition animations - component variant states - user flows and navigation
Retrieves activity log events from figma, allowing filtering by event types, time range, and pagination.
Retrieves detailed information about a specific webhook by its id, provided the webhook exists and is accessible to the user.
Retrieves all comments from an existing figma file, identified by a valid `file key`, returning details like content, author, position, and reactions, with an option for markdown formatted content.
Get component data with automatic simplification. returns clean, ai-friendly component structure.
Retrieves detailed metadata for a specific published figma component set using its unique `key`.
20 actions available