Figma MCP integration for AI agents.
Connect AI agents to Figma through 26 structured actions, including get component, create dev resources, delete comment, and render images. Review authentica…
- ACTION CONTRACTS
- 26
- AUTHENTICATION
- API key + OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Figma integration exposes
The Figma Agent App exposes 26 provider-backed actions for design and productivity work. Its current contract lets an authorized agent get metadata for a published figma component by key, create dev resources and attach them to figma file nodes, and delete a figma comment created by the authenticated user. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key and OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Figma account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Figma capabilities.
Showing 12 of 26 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_componentREADGet metadata for a published Figma component by key.
INPUTS: key
create_dev_resourcesWRITECreate dev resources and attach them to Figma file nodes.
INPUTS: devResources
delete_commentHIGH IMPACTDelete a Figma comment created by the authenticated user.
INPUTS: fileKey / commentId
render_imagesREVIEWRender selected Figma file nodes and return temporary image URLs.
INPUTS: fileKey / nodeIds / version / scale / format
delete_comment_reactionHIGH IMPACTDelete an emoji reaction created by the authenticated user.
INPUTS: fileKey / commentId / emoji
delete_dev_resourceHIGH IMPACTDelete a Figma dev resource from a main file.
INPUTS: fileKey / devResourceId
get_component_setREADGet metadata for a published Figma component set by key.
INPUTS: key
get_current_userREADGet the current Figma user associated with the credential.
get_dev_resourcesREADGet dev resources attached to a Figma main file.
INPUTS: fileKey / nodeIds
get_fileREADGet the JSON document for a Figma file or branch.
INPUTS: fileKey / version / nodeIds / depth / geometry
get_file_metadataREADGet lightweight metadata for a Figma file without fetching its full document.
INPUTS: fileKey
get_file_nodesREADGet JSON for selected node IDs from a Figma file or branch.
INPUTS: fileKey / nodeIds / version / depth / geometry
INPUT CONTRACTS
Know what the action needs before it runs.
get_component
keyREQUIRED- The unique Figma library asset key.
create_dev_resources
devResourcesREQUIRED- The dev resources to create.
delete_comment
fileKeyREQUIRED- The Figma file key or branch key from a Figma file URL.
commentIdREQUIRED- The Figma comment ID.
render_images
fileKeyREQUIRED- The Figma file key or branch key from a Figma file URL.
nodeIdsREQUIRED- Figma node IDs to fetch or render, for example `1:2` or `123:456`.
versionOPTIONAL- A specific Figma file version ID to read.
scaleOPTIONAL- The image scale factor supported by Figma.
formatOPTIONAL- The image format Figma should render.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Component
Get metadata for a published Figma component by key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_componentControl Create Dev Resources
Create dev resources and attach them to Figma file nodes. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_dev_resourcesVerify with Get Component Set
Get metadata for a published Figma component set by key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_component_setSAFETY BOUNDARY
Operate Figma with explicit limits
- Authorize Figma with API key and OAuth 2.0 and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_comment`, `delete_comment_reaction`, and `delete_dev_resource` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `file_dev_resources:write`, `file_comments:write`, `library_assets:read`, and `current_user:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Figma task completed successfully.
CONNECTION MODEL
API key + OAuth 2.0
Figma personal access token sent with the X-Figma-Token header. Create or manage tokens from Figma account settings: https://www.figma.com/developers/api#access-tokens
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 18
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Figma.