What can you do with the Figma integration?

LiveContext exposes 46 operations on Figma, covering webhook, analytics, dev resource and comment. Common uses include Link to source file, Token reporting and Design system metrics.

Which OAuth scopes does Figma require?

It depends on the operation: each one declares the scopes Figma requires for it. The most common are library_analytics:read (6 operations), team_library_content:read (3 operations), file_variables:read (2 operations) and folders:read (2 operations).

LiveContext

All integrations

Figma integration

Design and prototyping platform API for accessing design files, components, styles, and team resources. Read design file structures, export images, manage comments, browse component libraries, and access design tokens. Perfect for building design-to-code tools, design system documentation, asset export pipelines, and design collaboration integrations.

46 toolsOAuthAPI docs

Connect Figma How integrations work

Common Figma use cases

Link to source file
Token reporting
Design system metrics
Undo reaction
Audit webhooks
Real-time sync
Security audit
Audit style usage
Clean up comments
List file variants

What you can do with Figma

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 7 operations

POSTcreate_webhook_v2
Creates a new webhook subscription.
DELETEdelete_webhook
Deletes a webhook subscription.
GETget_team_webhooks_deprecated
DEPRECATED: Gets webhooks registered for a team.
GETget_webhook
Gets a specific webhook by ID.
GETget_webhook_requests
Gets webhook request history for the past week.
GETlist_webhooks_v2
Lists webhooks by context or plan with pagination.
PUTupdate_webhook
Updates a webhook subscription.

Analytics, 6 operations

GETget_library_analytics_component_actions
Gets time-series data for component actions in a library.
GETget_library_analytics_component_usages
Gets component usage counts grouped by dimensions.
GETget_library_analytics_style_actions
Gets time-series data for style actions in a library.
GETget_library_analytics_style_usages
Gets style usage counts grouped by dimensions.
GETget_library_analytics_variable_actions
Gets time-series data for variable actions in a library.
GETget_library_analytics_variable_usages
Gets variable usage counts grouped by dimensions.

Dev resource, 4 operations

POSTcreate_dev_resources
Bulk creates dev resources across multiple files.
DELETEdelete_dev_resource
Deletes a dev resource from a file.
GETget_dev_resources
Gets dev resources attached to nodes in a file.
PUTupdate_dev_resources
Bulk updates dev resources across multiple files.

Comment, 3 operations

DELETEdelete_comment
Deletes a comment from a Figma file.
GETget_comments
Retrieves all comments and annotations on a Figma file.
POSTpost_comment
Creates a new comment on a Figma file at specific coordinates.

Component, 3 operations

GETget_component
Retrieves detailed metadata for a specific component by its unique key.
GETget_file_components
Gets published components from a file library.
GETget_team_components
Lists all reusable components published in a team's component library.

Component set, 3 operations

GETget_component_set
Gets metadata for a specific component set by key.
GETget_file_component_sets
Gets published component sets from a file library.
GETget_team_component_sets
Gets paginated list of published component sets (variants) for a team.

File, 3 operations

GETget_file
Retrieves complete design file structure including all frames, components, and nodes.
GETget_file_meta
Retrieves file metadata without the full document structure.
GETget_project_files
Retrieves all design files within a specific project.

Reaction, 3 operations

DELETEdelete_comment_reaction
Removes an emoji reaction from a comment.
GETget_comment_reactions
Gets paginated emoji reactions on a comment.
POSTpost_comment_reaction
Adds an emoji reaction to a comment.

Style, 3 operations

GETget_file_styles
Gets published styles from a file library.
GETget_style
Gets metadata for a specific style by key.
GETget_team_styles
Retrieves all published styles from a team's style library.

Variable, 3 operations

GETget_local_variables
Gets local variables and collections from a file.
GETget_published_variables
Gets published variables from a library file.
POSTmodify_variables
Bulk creates, updates, and deletes variables and collections.

Image, 2 operations

GETget_file_image_fills
Gets download URLs for all images used in image fills within a file.
GETget_images
Exports design nodes as image files in various formats and scales.

Activity log, 1 operation

GETget_activity_logs
Gets activity log events for an organization.

Node, 1 operation

GETget_file_nodes
Retrieves specific design nodes by their IDs without fetching the entire file.

Payment, 1 operation

GETget_payments
Queries payment information for plugins, widgets, or files.

Project, 1 operation

GETget_team_projects
Lists all projects within a Figma team.

User, 1 operation

GETget_me
Retrieves the authenticated user's profile and account information.

Version, 1 operation

GETget_file_versions
Retrieves the complete version history of a Figma file.

OAuth scopes Figma requires

Each operation declares the scopes Figma requires for it.

library_analytics:readneeded by get_library_analytics_component_actions, get_library_analytics_component_usages, get_library_analytics_style_actions and 3 more
team_library_content:readneeded by get_team_components, get_team_component_sets, get_team_styles
file_variables:readneeded by get_local_variables, get_published_variables
folders:readneeded by get_project_files, get_team_projects
file_variables:writeneeded by modify_variables
org:activity_log_readneeded by get_activity_logs

Use Figma from Claude Code, Cursor or Codex

Connect Figma in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Figma operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Figma

Create your workspace
Sign up free. Nothing to install.
Connect Figma once
Add your Figma connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Figma integration FAQ

What can you do with the Figma integration?: LiveContext exposes 46 operations on Figma, covering webhook, analytics, dev resource and comment. Common uses include Link to source file, Token reporting and Design system metrics.
Which OAuth scopes does Figma require?: It depends on the operation: each one declares the scopes Figma requires for it. The most common are library_analytics:read (6 operations), team_library_content:read (3 operations), file_variables:read (2 operations) and folders:read (2 operations).