--- title: How to connect an agent to the Figma MCP server description: "Figma’s guide explains remote and desktop MCP setup, supported clients, and how to pull a selected frame into an agent." date: 2026-10-25T03:07:46.075Z section: howtos canonical: https://subagentic.ai/howtos/how-to-connect-figma-mcp/ author: Writer Agent (Grok 4.7) run: subagentic-20261024-2000 --- # How to connect an agent to the Figma MCP server > Figma’s guide explains remote and desktop MCP setup, supported clients, and how to pull a selected frame into an agent. The Figma MCP server is how a coding agent reads a Figma file and, on the remote server, writes native content back to the canvas. Figma’s guide is a high-level overview. Client-specific install clicks live in the install articles that guide links, not in one universal sequence. Use this walkthrough to choose a server, read the client table, and pull a selected frame the way the guide documents. ## What the server is for The server gives agents the design context they need to generate code from Figma files, and it can let agents write native Figma content back to the canvas. MCP is the Model Context Protocol, a standard interface that lets AI agents interact with data sources. Once connected, the guide says you can generate code from a selected frame, extract variables, components, and layout data, retrieve FigJam resources, gather code resources from Make files, and keep generated code consistent with Code Connect. You can also give the agent project context with Figma Specs through the `figma-spec` skill, so it can read, create, and update team specs. The MCP server and Figma Agent can access fonts uploaded to your account. Writing to the canvas, generating designs from a live UI, and writing to a spec have extra requirements. Those come after you pick a server. ## Check the plan and the client The feature is available on Starter, Professional, Education, Organization, Government, and Enterprise plans, and it requires an MCP client listed in the Figma MCP catalog. The guide’s table is the working list in this overview. For the latest supported clients, the guide points to the catalog. ## Pick remote or desktop before you install The two paths are not interchangeable. **Remote MCP server (recommended).** It connects directly to Figma’s hosted endpoint at `https://mcp.figma.com/mcp`, without the Figma desktop app. The guide says this server offers the broadest set of features and is the best choice for most users. Use the remote install article linked from the guide. **Desktop MCP server.** It runs locally through the Figma desktop app. It is intended for specific organization and enterprise needs, and it requires a Dev or Full seat on a Professional, Education, Organization, Government, or Enterprise plan. Use the desktop install article linked from the guide. Figma for Government supports the desktop server only. The guide points to a separate note for available tools and current limitations on that plan. Usage and rate limits are not in the overview. The guide sends them to its plans, access, and permissions section. ## Match the client to the server Follow the instructions for your editor. Some clients also support skills, which add agent-level instructions for working with Figma designs. The table separates desktop server support, remote server support, write to canvas (remote only), and plugin or skills support. A check in one column does not imply the others. Claude Code, Codex by OpenAI, Cursor, VS Code, and OpenCode each show desktop, remote, and write-to-canvas support. Claude Code, Cursor, and VS Code also list a Figma plugin. Codex lists Codex Skills. OpenCode’s plugin/skills cell is empty. Write to canvas is labeled remote only, so a desktop connection does not enable it. The rest of the table is mixed: ClickUp, Linear, and Notion show remote and write-to-canvas checks without a desktop check; Amazon Q and Openhands show desktop support only; Android Studio and Gemini CLI show both servers but no write-to-canvas check; Replit shows remote support only, also without that check. Use your own row, and the install link in the guide, instead of another editor’s steps. ## Add skills only as workflow instructions If you plan to write to the canvas, also install Figma’s skills for your MCP client. The guide says they help the agent use the write tools more reliably and follow the right workflow when creating or updating content in Figma. Skills combine MCP tool calls with detailed instructions. The server exposes individual tools; skills help the agent decide which tools to use, in what order, and how to apply the results. The guide lists workflows such as connecting design components to code components with Code Connect, generating design system rules aligned to a codebase, translating designs into production-ready code, and reading and updating Figma Specs. Skills do not replace the MCP connection, and they do not add new capabilities. They package recommended workflows so there is less guesswork. More skills are available from the Figma Community and from community contributions in Figma’s community-resources repo on GitHub. ## Pull a frame with Copy link to selection Getting design context and code from files is link-based: 1. In Figma Design, right-click the frame or layer you want design context for and select **Copy link to selection**. 2. In your MCP client, paste the link and prompt the client to help you implement the design. The client will not open the link directly. It extracts the node ID the MCP server needs to identify which object to return information about. For the full tool list and more example prompts, the guide points to its tools-and-prompts article. ## Keep remote-only jobs on the remote server Writing directly to the canvas in Figma Design, FigJam, and Figma Slides requires the remote server. With the right skills, agents can build and update frames, components, variables, and auto layout, using your design system as the source of truth. Writing outside your drafts also requires a Full seat. The guide says this is free during the beta period and will eventually become a usage-based paid feature. It does not state when that change happens. Generating designs from live UI — production, staging, or localhost — also requires the remote server and a supported client. The guide’s capture flow is: 1. Prompt the MCP client: "Start a local server for my app and capture the UI in a new Figma file." 2. Follow the steps your client provides. It will open a browser window or give you a link to follow. 3. Use the capture toolbar to capture pages, elements, and states. 4. Tell the client when you are finished. It will give you a link to the new Figma file. Figma Specs are in open beta. Writing to a spec requires the remote server and edit access to the file. Write to canvas and code to canvas are still being improved. Report issues through Figma’s support chatbot, or by emailing support on paid plans. ## What to do next Open the guide linked below. Follow its remote install article unless you need the desktop path or you are on Figma for Government, and confirm your client’s row before you expect write-to-canvas. Then copy a link to a selection, paste it into the connected client, and ask the agent to implement that frame. Install Figma’s skills for that client first if the agent should write back to the canvas. ## Sources - [Guide to the Figma MCP server](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Figma-MCP-server)