← All connection guides

How to connect Codex to Figma

Connect Codex to the official Figma MCP server and verify access to a specific frame before requesting implementation.

Free guide · Updated

Based on official documentation · Checked

Ask your agent

Copy the prompt and paste it into your assistant.

Quick answer

Figma documents both a Codex app plugin and a Codex CLI connection to its remote MCP server. Choose the path matching your client. Installing a plugin and adding an MCP endpoint are separate setup methods; neither grants access to every Figma file.

Before you start

Have access to a small test file with a clearly named frame. Confirm the Figma account and workspace you intend to authorize, and check current seat and usage limits in the vendor documentation. Copy the link to the exact frame rather than a dashboard URL.

Option A: Codex app

Open Plugins in the Codex app, find Figma, install it and complete the access flow. Return to Codex and confirm the plugin is connected. Use this path when the plugin is available to your account; organization policies may affect installation.

Option B: Codex CLI

For the terminal client, add the official remote server. Complete the requested Figma sign-in and access approval. The remote route does not require the Figma desktop app. Manual MCP setup does not itself install all of the vendor skills bundled with a plugin.

codex mcp add figma --url https://mcp.figma.com/mcp

Practice

Verify access before generating code

  1. Provide the link to one test frame. Ask Codex to use Figma tools to inspect it and report its actual text, dimensions and component structure. Compare the response with the frame in Figma.

Output: Retrieved design context matching the specified frame; the server/tool used is identifiable in the run.

Use the context for implementation

After confirming the read, ask for a small implementation using that frame and the conventions of your existing project. Review layout, typography and assets against the source. A plausible screenshot or attractive result without retrieved design context does not prove the connection.

Troubleshooting

Connected but denied: check access to that exact file under the authorized account. Wrong content: verify the node/frame link. Tools missing: check the selected client setup and organization restrictions. A large frame request should be narrowed before repeated retries. Inspect the current error before treating a limit as an authentication failure.

Disconnect

Remove or disable the connection created in the selected client and revoke its authorization when needed. Do not remove a shared team plugin unintentionally. Disconnect from the same client you configured; app and CLI connections are managed separately.

Sources

Read the primary material