[MCP][Figma] `generate_figma_design` is not exposed in Codex tool catalog — request parity / guidance

Resolved 💬 2 comments Opened Feb 17, 2026 by TU-hayaoki Closed Feb 17, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

CLI + Codex App (macOS) + VS Code Extension

What feature would you like to see?

Request

Please support (or explicitly clarify non-support for) the Figma MCP tool / workflow generate_figma_design in Codex.

Figma’s developer docs list generate_figma_design but note it is “Claude Code only / remote only”, and describe a client-side capture workflow (start a local server, inject a script, open a browser window, capture via a toolbar, then write layers to a Figma Design file / clipboard).
Codex users would like an equivalent capability, or at minimum a clear official stance and guidance.

Current behavior (Codex)

When using Codex CLI (latest) with the remote Figma MCP endpoint, the tool catalog does not include generate_figma_design (see “Additional information” for the exact output).

Expected behavior / outcome

One of the following would be very helpful:
1) Parity support: Codex can drive an equivalent generate_figma_design flow (capture live UI from localhost/staging/prod and write editable layers into a Figma Design file / clipboard), or
2) Clear decision + guidance: If this is blocked (e.g., Figma-side allowlisting / policy, security model, missing client-side orchestration), please confirm the blocker and recommend the official workflow for Codex users, and ideally surface a clearer capability/error message.

Why this matters

Many teams want a unified agent workflow in Codex. Today, the “Live UI → Figma Design” path appears gated behind “Claude Code to Figma”, even though Codex is listed as an MCP-capable client in Figma’s overview docs.

References

Additional information

Repro / observation

1) Configure Figma MCP remote server in Codex CLI (OAuth) and authenticate successfully.
2) List MCP servers / tool catalog in Codex CLI.
3) Observe that generate_figma_design is not present in the Figma tools list.

Tool catalog output (Codex CLI)

Command used: <paste the exact command here>

Output:

• figma
  • Status: enabled
  • Auth: OAuth
  • URL: https://mcp.figma.com/mcp
  • Tools: add_code_connect_map, create_design_system_rules, generate_diagram,
    get_code_connect_map, get_code_connect_suggestions, get_design_context,
    get_figjam, get_metadata, get_screenshot, get_variable_defs,
    send_code_connect_mappings, whoami
  • Resources: ... (omitted)

View original on GitHub ↗

2 Comments

etraut-openai contributor · 6 months ago

Codex doesn't have any special-case knowledge of individual MCP servers, so it wouldn't make sense to include a "Figma-specific workflow". If you suspect a bug in Codex's handling of MCPs, please clarify. If you suspect a bug in the Figma MCP (e.g. code that gates its functionality on Claude Code), please report that to Figma.

TU-hayaoki · 6 months ago

@etraut-openai
Thanks — understood.

I verified on the latest Codex CLI that the Figma remote MCP endpoint (https://mcp.figma.com/mcp) does not include generate_figma_design in the tool catalog (it’s missing from the Tools: list), which suggests this is likely gated/omitted server-side rather than something Codex is filtering.

Given Figma’s docs explicitly note generate_figma_design as “Claude Code only / remote only”, I’ll report this as a feature request / limitation to Figma.

In the meantime, I’ll consider using Claude Code as a workaround for this “live UI → Figma” flow.

Feel free to close this issue.