Connect Figma (remote MCP) to Codex
Figma's hosted MCP server with design context and beta canvas writes. Available on all plans, with tight call limits on Starter, View and Collab seats.
MCP serverOfficialChecked 2026-11-16
Before you start
- Codex installed (see its MCP documentation (opens in a new tab)).
- Figma (remote MCP) is available on macOS, Windows, Linux and the web.
- Starter plan and View/Collab seats get 6 tool calls a month; Dev/Full seats on paid plans get 200 a day.
Step 1: Add Figma (remote MCP) to Codex
Add it from the terminal
Saves the server to
~/.codex/config.toml, so it works in every project.Terminal codex mcp add figma-remote --url https://mcp.figma.com/mcpOr edit the config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.figma-remote] url = "https://mcp.figma.com/mcp"Good to know- Sign in once with
codex mcp login figma-remote.
- Sign in once with
Step 2: Check it's connected
Terminal codex mcp listIn a Codex session, run
/mcpto see connected servers and their tools.Step 3: Try a first request
Ask Codex something that only works with Figma (remote MCP) connected:
Say to Codex Here's a link to a Figma frame: <paste link>. Summarise its layout and the variables it uses.
If it doesn't work
- Codex reads
~/.codex/config.toml. A project.codex/config.tomlis only read in projects you have trusted. - Codex doesn't expand
~or environment variables incommand. Use a full path in the config file. - Servers that need a sign-in: run
codex mcp login <name>.





