Skip to main content
연두 정
New Member
Aug 28, 2026 5:05 AM UTC
Question

The same `use_figma` request sometimes requires a full seat, and sometimes doesn't

Hello,

I’m using the Figma MCP server with Codex, and I’m experiencing an issue with use_figma: the same request sometimes succeeds, while at other times it returns a message saying that a Full Seat is required (I currently have a Dev Seat.)

According to the official FAQ, read-only operations should still be available with a Dev Seat, so I expect the request to always succeed.

Below is a technical summary generated by Codex.

----

Environment

  • MCP client: Codex
  • Figma MCP: Remote MCP
  • Plan: Enterprise
  • Seat: Dev
  • File key: N2i5Xfv16eonu10Nmes4iH
  • Target node: 29583:56677
  • Node type: INSTANCE

Request

The use_figma request contained the following parameters:

{
"fileKey": "N2i5Xfv16eonu10Nmes4iH",
"description": "Read-only comparison of Figma Instance 29583:56677 with its Main Component; do not modify any nodes",
"skillNames": "resource:figma-use",
"code": "<4071-character JavaScript code>"
}

The complete JavaScript payload is attached as use-figma-read-only-reproduction.js.txt.

 

Identical calls with different results

The two calls below used identical parameters and JavaScript code.

 

Denied call

Timestamp: 2026-08-27 06:39:21 UTC
Figma Debug UUID: 8da991fe-229b-45ec-9a5b-d6dbfb3340f4

Response:

To use MCP tools that make edits, you'll need a Full seat.

Successful call

Timestamp: 2026-08-27 06:44:41 UTC
Figma Debug UUID: 5d599605-5808-44da-8347-61c90478fae7

This call successfully returned the complete read-only comparison result.

5 replies

Giorgio Fellipe
New Member
Oct 15, 2026 3:09 PM UTC

Same here, read-only use_figma (exporting local variables/text styles, nothing mutated) on the same file flips between allowed and "To use MCP tools that make edits, you'll need a Full seat."

- 2026-09-28 17:20 UTC denied: 0740e18c-a9d9-44c6-9724-fdbf08c3040f
- same day, later, the same export script succeeded
- worked consistently until 2026-10-02
- 2026-10-15 15:04 UTC denied: 661bad5d-79fe-49f6-89c3-eab32e44eb19
- 2026-10-15 15:05 UTC denied on a 2-line read (getLocalVariableCollectionsAsync only): 4a206baf-d9b5-4716-88e4-b56854bd2c53

Remote MCP from Claude Code. Is read-only use_figma supposed to work on a Dev seat or not? the FAQ says Dev seats keep read access to variables, but the only way to read collections with modes and aliases is use_figma.

adamsmasher
Figmate
Figmate
Oct 17, 2026 7:58 PM UTC

Thanks for your reply, ​@Giorgio Fellipe, and thanks ​@연두 정 for including timestamps and debug IDs. I can see why getting different results from the same read-only request is confusing.

 

​@Giorgio Fellipe , could you share the exact two-line script that failed and your Figma plan? Please also confirm that whoami reports a Dev seat on the plan that owns the file; also, be sure keep your email address private when sharing. That will help narrow down the permission check alongside the debug IDs you’ve already provided.

 

​@연두 정 , are you still seeing this? Let me know and I can include your examples in any potential I share with the team.

Daria Matviienko
New Member
Oct 29, 2026 3:05 PM UTC

Same symptom here on an Enterprise plan, Dev seat, remote MCP server. whoami reports seat Dev, tier enterprise, on the plan that owns the file.

Adding what was asked for on 17 Oct: the exact script, plus a measurement that narrows what triggers the refusal.

In our case it correlates with one thing — the script contains an assignment to a figma.* property. The script is read-only: one page switch, one assignment, one return, and it creates nothing.

const node = await figma.getNodeByIdAsync('NODE-ID');

let p = node; while (p && p.type !== 'PAGE') p = p.parent;

await figma.setCurrentPageAsync(p);

const a = node.findAllWithCriteria({ types: ['TEXT'] }).length;

figma.skipInvisibleInstanceChildren = false;

const b = node.findAllWithCriteria({ types: ['TEXT'] }).length;

return { countAtDefault: a, countWithFalse: b };

Measured on 29 October 2026, in one session, on one file, from one account:

5 calls whose script carried the assignment — 1 succeeded, 4 were refused with "To use MCP tools that make edits, you'll need a Full seat."

3 calls with no assignment of any kind — all 3 succeeded.

One success and one refusal came from byte-identical scripts about a minute apart, so it is not deterministic.

Debug UUIDs for the refusals: 8a142868-de12-4fa7-8506-9521f61a64b9, 0b952fa9-23d9-4706-be4e-49a5f646a33b, 6d185104-5a20-4467-81fe-71cde55bdd4d, 0abd471b-df28-4026-b91e-d4b7ce05a716

skipInvisibleInstanceChildren is a traversal setting on the plugin runtime. It changes nothing in the document, and there is no other route to text inside hidden layers of component instances — a manual walk of .children returns the same count as the default traversal. The practical effect on a Dev seat is that this text cannot be read reliably: on one frame the default traversal returned 2,501 TEXT nodes and the same traversal with the flag off returned 3,584.

adamsmasher
Figmate
Figmate
Oct 29, 2026 9:12 PM UTC

Thanks for your reply, ​@Daria Matviienko, and I appreciate all the detail you included and that you’ve run a whoami command to confirm basic seat and file information.

 

I’ve created a ticket for you with out support team and included this information, though you’re welcome to reply to the email and include anything else you feel is relevant. Everything you’ve included here gives us a lot to work with in figuring out why those particular calls were refused when one succeeds. Thanks for your patience, and let us know if you have any questions!

Peng Xiao
New Participant
Nov 22, 2026 12:51 AM UTC

The "Full seat" message is about edits: Figma's official server needs a Full seat to write outside your drafts, and a Dev seat only writes in drafts. That may explain why some calls pass and others fail, since a script that assigns to a figma.* property counts as an edit.

 

If you use Codex on a Mac, I built FigmaMCP, a local plugin that edits the file open in Figma desktop. No token, no call quota, not affiliated with Figma: figmamcp.dev