Private AI integrates with Figma through the official Figma MCP, enabling AI agents to read, create, and edit Figma designs directly.
The integration uses OAuth authentication. Usage limits depend on your Figma account’s plan.

​
For Users

Include Figma links in your task descriptions to guide AI implementation.
Task description containing Figma design links
## Design
- **Website:** [Figma - App Design](https://figma.com/design/FILE_KEY/...)
- **Mobile:** [Figma - App Design](https://figma.com/design/FILE_KEY/...)

​
What the AI Can Do

CapabilityDescription
ReadView layouts, styles, components, and specifications
CreateGenerate new Figma designs and diagrams
EditModify existing designs directly in Figma
ExportExtract assets, colors, and typography values

​
Example Workflow

1

Create task with Figma links

Write a task description including links to your Figma designs.
2

Start the task

Assign the task to Claude Code. The agent detects Figma links automatically.
3

AI works with designs

Claude Code reads designs, extracts specifications, and generates matching code.
Implemented login page UI
Specify which design to use if you have multiple: “Implement using the Website design linked above.”

​
For Administrators

​
Authentication

The Figma MCP uses OAuth authentication. No manual API key configuration required.
All Figma operations are tied to the authenticated Figma account. Ensure the account has appropriate permissions for required files.

​
Student Account Limitations

If using a Figma Student/Education account, be aware of these restrictions:
When accessing files created by other accounts, rate limits may apply to the file owner’s account, not yours. This can affect performance when working with externally-owned designs.
Files created by Student accounts can only be edited by non-Student users for 7 days. After that, they become view-only. Team members without Student accounts will have limited long-term access.
To avoid limitations, create all design files directly within the authenticated Student account rather than inviting external files.

​
Best Practices

  • Create designs within the authenticated Figma account
  • Use clear naming for files and frames
  • Group related designs (website and mobile) together
  • Mark designs as “Ready for Dev” when finalized

​
Troubleshooting

  • Verify the authenticated account has access to the file
  • Check the file URL is correct
  • Ensure the file is not private or restricted
  • Reduce frequency of Figma API calls
  • Check if file is owned by external account (may hit their limits)
  • Wait and retry after a few minutes
  • Verify the authenticated account has edit permissions
  • For Student accounts, ensure the file is owned by the same account
  • Check if 7-day edit window has expired for non-Student collaborators