Figma (remote MCP)
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.
Connect it directly in your agent
https://mcp.figma.com/mcpStarter plan and View/Collab seats get 6 tool calls a month; Dev/Full seats on paid plans get 200 a day.
Set it up in your agent
Add it from the terminal
Run this in your project folder. It saves the server for you, in this project only.
Terminal claude mcp add --transport http figma-remote https://mcp.figma.com/mcpOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Teammates approve it the first time Claude Code starts..mcp.json { "mcpServers": { "figma-remote": { "type": "http", "url": "https://mcp.figma.com/mcp" } } }
- The first time, run
/mcpin a session and choose the server to sign in.
Check it works
claude mcp listStart a session and run /mcp to see the server, its status and its tools.
Or add it to the project
Add this to
.cursor/mcp.json, or to~/.cursor/mcp.jsonto use it in every project..cursor/mcp.json { "mcpServers": { "figma-remote": { "url": "https://mcp.figma.com/mcp" } } }
- Cursor opens a sign-in page the first time it connects.
Check it works
Open Cursor Settings, find the MCP section and check the server is enabled with its tools listed.
Add it from the terminal
Adds the server to your VS Code profile, so it works in every workspace.
Terminal code --add-mcp '{"name":"figma-remote","type":"http","url":"https://mcp.figma.com/mcp"}'Or add it to the workspace
Add this to
.vscode/mcp.jsonand commit it to share it with your team..vscode/mcp.json { "servers": { "figma-remote": { "type": "http", "url": "https://mcp.figma.com/mcp" } } }
- VS Code asks you to sign in the first time the server starts.
Check it works
Run MCP: List Servers from the Command Palette, then open Copilot Chat in Agent mode and check the tools picker.
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"
- Sign in once with
codex mcp login figma-remote.
Check it works
codex mcp listIn a Codex session, run /mcp to see connected servers and their tools.
Add it from the terminal
Run this in your project folder. It saves the server to the project's
opencode.json.Terminal opencode mcp add figma-remote --url https://mcp.figma.com/mcpOr edit the config file
Add this to
opencode.jsonat the project root.opencode.json { "$schema": "https://opencode.ai/config.json", "mcp": { "figma-remote": { "type": "remote", "url": "https://mcp.figma.com/mcp", "enabled": true } } }
- Sign in once with
opencode mcp auth figma-remote.
Check it works
opencode mcp listStart OpenCode in the project; the server's tools are available to the agent straight away.
Figma (remote MCP) only accepts approved clients, and Google Antigravity isn't one of them yet.
Works in Google Antigravity: Figma (desktop MCP)
Add it from the terminal
Run this in your project folder. It saves the server to the project's
.gemini/settings.json.Terminal gemini mcp add --transport http figma-remote https://mcp.figma.com/mcpOr edit the config file
Add this to
.gemini/settings.jsonin your project, or to~/.gemini/settings.jsonto use it in every project..gemini/settings.json { "mcpServers": { "figma-remote": { "httpUrl": "https://mcp.figma.com/mcp" } } }
- The first time, run
/mcp auth figma-remotein a session to sign in.
Check it works
gemini mcp listIn a Gemini CLI session, run /mcp to see each server, its status and its tools.
Figma (remote MCP) only accepts approved clients, and Devin Desktop isn't one of them yet.
Works in Devin Desktop: Figma (desktop MCP)
Figma (remote MCP) only accepts approved clients, and Zed isn't one of them yet.
Works in Zed: Figma (desktop MCP)
Figma (remote MCP) only accepts approved clients, and Cline isn't one of them yet.
Works in Cline: Figma (desktop MCP)
For Claude Code sessions
Saves the server to your Claude Code user settings, so every Conductor workspace gets it.
Terminal claude mcp add --scope user --transport http figma-remote https://mcp.figma.com/mcpFor Codex sessions
Saves the server to
~/.codex/config.toml, which Codex sessions in every workspace read.Terminal codex mcp add figma-remote --url https://mcp.figma.com/mcpOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Claude Code sessions in every workspace on that branch pick it up..mcp.json { "mcpServers": { "figma-remote": { "type": "http", "url": "https://mcp.figma.com/mcp" } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.figma-remote] url = "https://mcp.figma.com/mcp"
- Start a new session in Conductor after adding a server, so the agent loads it.
- To sign in, open Conductor's MCP status dialog and use the sign-in action on the server's row.
Check it works
claude mcp listIn a Conductor session, click the plug icon in the composer or run /mcp-status to see each server's status.
More in Design tools
- PaperAI-native design canvas built on HTML and CSS. Its MCP server lets agents read artboards, export JSX and write new designs straight onto the canvas.
- Figma (desktop MCP)Figma's local MCP server, served by the desktop app. Gives agents design context, variables and code-connect data for the selected frame.
- PenpotOpen-source design and prototyping tool that runs in the browser or on your own server. Its official MCP server lets agents read and change the page you have open.
