Overview
What Figma MCP Server does
Figma's official MCP server connects design files to coding and agent workflows. The recommended hosted endpoint can inspect frame structure, retrieve variables and screenshots, export assets, use Code Connect mappings, search design systems, and access Figma Make resources. Its newer write-oriented tools can create files, diagrams, and editable canvas content when the client and account support them. A desktop endpoint remains available for local, selection-based workflows, but the hosted server has the widest tool set and does not require the Figma desktop app to stay open.
Best for
- Implementing interfaces from Figma while preserving design-system context
- Auditing variables, component mappings, layout metadata, and visual references
- Supported agent workflows that need to create diagrams or native Figma layers
Not ideal for
- Clients that are not in Figma's supported MCP catalog
- Expecting the server's React-like design context to be production-ready application code
Capabilities
What an agent can do
- 01
Return structured design context, sparse metadata, variables, and screenshots
- 02
Read and update Code Connect mappings for codebase-aligned components
- 03
Download or upload assets and retrieve Figma Make resources
- 04
Search subscribed and available design libraries
- 05
Create Figma files, FigJam diagrams, or editable canvas content on supported remote workflows
Representative tools and operations
get_design_contextget_metadataget_screenshotget_variable_defsget_code_connect_mapsearch_design_systemdownload_assetscreate_new_filegenerate_diagramuse_figmawhoami
Installation
Connect Figma MCP Server
Use the publisher’s current instructions as the source of truth. The examples below were checked on .
Claude CodeAdd the recommended hosted server
claude mcp add --transport http figma https://mcp.figma.com/mcpRun /mcp, choose Figma, and complete the browser authorization flow.VS CodeAdd the remote URL to mcp.json
https://mcp.figma.com/mcp{
"inputs": [],
"servers": {
"figma": {
"url": "https://mcp.figma.com/mcp",
"type": "http"
}
}
}Desktop-supported clientsConnect to the Figma desktop app
http://127.0.0.1:3845/mcpEnable the MCP server from Figma Dev Mode before connecting to the local URL.Trust and access
Authentication and security notes
Authentication: The hosted endpoint uses Figma authorization and respects the signed-in user's plans, seat, file permissions, and feature availability.
Review before connecting
- Authorize only the files and organization context appropriate for the agent's task.
- Write tools can change shared design files; confirm target file, permissions, and intended scope before mutation.
- Downloaded assets and design text may be confidential and should follow the same handling rules as the source file.
Known limitations
- Only clients accepted into Figma's MCP catalog can connect to the hosted service.
- Remote workflows require node or file links; selection-based prompting is a desktop-server feature.
- Tool availability varies by remote versus desktop server, client, account plan, seat, file type, and ongoing beta rollout.
- Large frames can exceed a client's MCP output budget and may need metadata-first, node-by-node retrieval.
Evidence
Sources used for this guide
Facts were checked against primary publisher material. Descriptions and guidance are original Graphify summaries.
FAQ
Questions about Figma MCP Server
Should I use Figma's remote or desktop MCP server?
Use the remote server for the broadest tool set and link-based access. Choose the desktop endpoint when local selection-based context is central to the workflow.
Does get_design_context return finished production code?
No. It returns agent-friendly design context. The coding agent must translate that context into the project's framework, components, accessibility rules, and conventions.
