Skip to main content
Question

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

  • August 28, 2026
  • 0 replies
  • 2 views

연두 정

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.