Skip to content
Custom Connectors

Full read-write Claude connector for Figma

Let Claude comment and manage variables in Figma

Stop clicking through frames to leave review notes and update variables by hand. A custom REST connector lets Claude fetch file and node details, post comments where they belong, reply to threads during a review, and update variables, applying each change only once you approve.

Figma is the collaborative design tool where teams build interfaces, design systems, and FigJam boards. People want Claude to do more than read a file: to comment on frames, manage variables, and update design content where the work already lives.

What is a Figma MCP server?

A Figma MCP server is a small hosted service that exposes Figma's data and actions to Claude over the Model Context Protocol, so Claude can issues, code, and incidents inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Figma's current connector do today?

Today, Figma ships a Dev Mode MCP server that can both read context and write native content to the canvas, including building and updating frames, components, and variables through the Plugin API. A custom REST connector is different: it adds OAuth-based hosted access and scoped, human-in-the-loop control over the comment and variable workflows the REST API supports.

What does full read-write Figma access unlock?

A custom REST Figma connector lets Claude fetch file and node details, list comments, post and reply to comments pinned to specific frames, and read or update variables once you approve. The comment review and variable bookkeeping that used to mean manual clicking happen through scoped, approval-gated tools instead.

  • Post a comment pinned to a specific frame or node
  • Reply to existing comments during a design review
  • Fetch a file and read its nodes, layout, and properties
  • Summarize unresolved comments across a file before a handoff
  • Read or update variables on a Figma Enterprise plan to align with the design system

Can Claude post comments on a Figma file?

Yes. A custom REST Figma connector lets Claude post comments pinned to a specific frame or node, and reply to existing comments during a design review. It fetches the surrounding nodes and layout first, so the note lands on the right spot instead of beside it.

Can Claude read a Figma file and summarize comments?

Yes. Claude can fetch a file and read its nodes, layout, and properties for context, then summarize unresolved comments across the file before a handoff. Reads and writes are separated tools, so you can keep Claude review-only or let it post comments once you approve each step.

Can Claude manage variables in Figma?

On a Figma Enterprise plan, Claude can read and update variables to align a file with your design system through the REST API. Each write is gated behind your confirmation, and the connector authenticates as your account, so it never reaches more files or teams than you already can.

How a Figma connector works

We build a small MCP server that authenticates to Figma with OAuth 2.0 and the narrowest scopes the work needs. Read tools (fetch file, read nodes, list comments) and write tools (post comment, reply to comment, update variables) are separated, and write actions require your confirmation. Claude only ever has the access your own Figma account already has. Editing layer names, text, or component properties runs through Figma's Dev Mode MCP server and Plugin API, not the REST connector.

Frequently asked questions

Can Claude actually write to a Figma file, not just read it?
It depends on the surface. The REST API a hosted OAuth connector uses can write comments and, on Enterprise plans, variables, so a custom connector exposes those as scoped, approval-gated tools. Renaming layers and editing text or component properties run through Figma's Dev Mode MCP server and Plugin API, which write native content to the canvas.
Will Claude delete layers or change my design without approval?
No. Every write is a gated tool that runs only after you confirm. Claude can prepare a comment to post or a variable update to apply, but nothing lands until you approve that specific step. Canvas edits made through the Dev Mode MCP server are likewise applied only when you accept them. You decide what stays manual.
Does the connector get more access to my files than I have?
No. The connector authenticates as your account through OAuth and inherits your existing Figma permissions. It can only reach the files and projects you can already open, and it never grants Claude more access to a team or design file than you already have.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.