Figma MCP server

Read from the package source without running it. The installed server may list more.

• add_comment_reaction

  Add an emoji reaction to a file comment. Reactions allow users to quickly respond to comments with emoji expressions.

• add_file_commentwrite action

  Posts a new comment on a file or replies to an existing root comment. Use the comment_id parameter to reply to a specific comment.

• bulk_modify_variables

  Bulk create, update, and delete variables, variable collections, modes, and mode values in a file. Changes are applied atomically in a defined order: collections, then modes, then variables, then mode values.

• create_dev_resourceswrite action

  Bulk create dev resources across multiple files. Successfully created resources are returned in the links_created array, while any resources that fail validation appear in the errors array with failure reasons.

• delete_commentwrite action

  Deletes a specific comment from a file. Only the comment author is permitted to delete their own comments.

• export_file_json

  Export a Figma file as JSON, including document structure, components, and optional metadata. Supports partial exports by node ID and configurable depth traversal.

• get_component

  Retrieve detailed metadata for a specific component using its unique identifier. This operation returns comprehensive information about the component's configuration and properties.

• get_component_set

  Retrieve metadata for a published component set using its unique identifier. Returns detailed information about the component set configuration and properties.

• get_current_user

  Retrieve the profile and account information for the currently authenticated user. This endpoint requires valid authentication credentials.

• get_file_metadata

  Retrieve metadata for a file or branch. Provide either a file key or branch key to access file information.

• get_file_nodes

  Retrieve specific nodes from a Figma file as JSON objects. Extract node data by providing node IDs, with optional support for vector geometry, nested traversal depth, and plugin data.

• get_style

  Retrieve detailed metadata for a specific style using its unique identifier. Use this to fetch style configuration and properties.

• get_webhook

  Retrieve a webhook configuration by its ID. Use this to fetch details about a specific webhook including its URL, events, and status.

• list_activity_logs

  Retrieve a list of activity log events filtered by type, time range, and ordering. Useful for auditing, monitoring system changes, and tracking user actions.

• list_comment_reactions

  Retrieves a paginated list of reactions left on a specific comment. Use this to see all emoji reactions and their authors for a given comment.

• list_component_sets

  Retrieve a paginated list of published component sets available in a team's library. Use pagination to manage large result sets efficiently.

• list_component_sets_file

  Retrieve all published component sets available in a file library. This operation requires a main file key and cannot be used with branch keys.

• list_dev_resources

  Retrieve development resources associated with a file. Optionally filter results to specific nodes within the file.

• list_file_comments

  Retrieves all comments left on a file. Supports both file keys and branch keys for accessing comments across different file versions.

• list_file_components

  Retrieve a list of published components available in a file library. Only main file keys are supported, as components cannot be published from branch files.

• list_file_styles

  Retrieve a list of published styles available in a file library. Styles can only be published from main files, not from branches.

• list_file_versions

  Retrieve the version history of a file to see how it has evolved over time. Use the returned version information to render a specific version via another endpoint.

• list_image_fills

  Retrieve download URLs for all images used in image fills within a Figma document. Image URLs are valid for up to 14 days and can be located by their imageRef attribute in Paint objects from the file endpoint.

• list_library_component_actions

  Retrieve analytics data for component actions within a library, aggregated by the specified dimension (component or team). Use this to analyze usage patterns and activity metrics across your design library.

• list_library_component_usages

  Retrieves analytics data on how components from a library are being used, with results grouped by the specified dimension (component or file).

• list_library_style_actions

  Retrieve analytics data for style actions in a library, aggregated by the specified dimension (style or team). Use date parameters to filter results to a specific time range.

• list_library_style_usages

  Retrieves analytics data on how styles are used within a library, aggregated by the specified dimension (style or file). Use this to understand style adoption and usage patterns across your design library.

• list_library_variable_actions

  Retrieve analytics data for variable actions within a library, aggregated by the specified dimension (variable or team). Use date parameters to filter results to a specific time range.

• list_library_variable_usages

  Retrieves analytics data on how variables are used within a library, aggregated by the specified dimension (variable or file). Use this to understand variable usage patterns and dependencies.

• list_local_variables

  Retrieve all local variables created in a file and remote variables referenced within it. This operation is restricted to full members of Enterprise organizations and supports examining variable modes and bound variable details.

• list_payments

  Retrieve payment information for a user on a specific Community file, plugin, or widget. You can only query resources that you own.

• list_project_files

  Retrieve all files within a specified project. Optionally include branch metadata for files that contain branches.

• list_published_variables

  Retrieve all variables published from a file, including their subscription IDs and last published timestamps. Available only to full members of Enterprise organizations.

• list_team_components

  Retrieve a paginated list of published components available in a team's component library. Use pagination to manage large result sets efficiently.

• list_team_projects

  Retrieve all projects within a specified team that are visible to the authenticated user. Only projects accessible to the token owner or authenticated user will be returned.

• list_team_styles

  Retrieve a paginated list of published styles from a team's design library. Use pagination to control the number of results returned per request.

• list_webhooks

  Retrieve webhooks filtered by context or plan. Use context_id to get webhooks for a specific context, or plan_api_id to retrieve all webhooks across all accessible contexts with pagination support.

• remove_comment_reactionwrite action

  Remove a reaction from a comment. Only the user who added the reaction can delete it.

• remove_dev_resourcewrite action

  Remove a dev resource from a file. This operation permanently deletes the specified dev resource and cannot be undone.

• render_node_images

  Render images from specified nodes in a file. Returns a map of node IDs to image URLs, with null values indicating failed renders. Rendered images expire after 30 days.

• update_dev_resourceswrite action

  Bulk update dev resources across multiple files. Successfully updated resource IDs are returned in the response, while any resources that fail to update are included in an errors array.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 62% of 1,337 Media servers

Tools

41

the typical Media server has 7

Tools that change things

15%

typical: 4%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 715 Media servers

Figma: common questions

Is Figma MCP server safe?

Mostly: it is graded B (80/100). Read the Figma safety report

How do I install Figma?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Figma need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Figma maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.6.

What can I use instead of Figma?

Servers from other publishers that do the same job: Figma UI MCP server, Codesign MCP server and Mimic AI MCP server.

How does Figma compare with other Media MCP servers?

safety score 80/100 (higher than 62% of 1,337 Media servers); tools 41 (the typical Media server has 7); tools that change things 15% (typical: 4%. Fewer write tools means less an agent can break). Full comparison.