
How to add Figma MCP Server (Official Remote) to Claude Desktop
Official Figma server that brings design context, variables, and components into AI coding tools. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.
Last updated June 15, 2026 ยท 120โ ยท http ยท oauth ยท official
Claude Desktop config for Figma MCP Server (Official Remote)
Add MCP server URL https://mcp.figma.com/mcp (HTTP) and sign in via Figma OAuth{
"mcpServers": {
"figma-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.figma.com/mcp"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Setup steps
- 1Open Claude Desktop โ Settings โ Developer โ Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
- 2Paste the Figma MCP Server (Official Remote) config below under the top-level "mcpServers" key.
- 3Fill in any placeholder secrets (API keys, paths) in the snippet.
- 4Save the file, then fully quit and reopen Claude Desktop.
- 5Open a chat and confirm Figma MCP Server (Official Remote)'s tools appear under the ๐ tools menu.
Before you start
- An active Figma account. The remote server works on all seats/plans; the local desktop server needs a Dev or Full seat on a paid plan.
- An MCP-compatible client (VS Code + Copilot, Cursor, Windsurf, Claude Code, Gemini CLI, etc.).
- For the remote server: OAuth โ you authorize in the browser on first connect; no token to copy.
- For the local server: the Figma desktop app running, with the Dev Mode MCP server enabled in preferences.
- Acceptance of the Figma Developer Terms; write-to-canvas usage may be metered/paid after beta.
What Figma MCP Server (Official Remote) can do in Claude Desktop
get_design_contextGet the full design context (layout, components, styles) for the current selection or a layer.
get_metadataReturn a sparse XML map of layer IDs, names, types, positions, and sizes.
get_variable_defsReturn the variables and styles (design tokens) used in the selection.
get_screenshotCapture a screenshot of the current selection for visual grounding.
get_code_connect_mapRetrieve mappings between Figma nodes and Code Connect code components.
add_code_connect_mapMap a Figma node ID to its corresponding code component in your codebase.
search_design_systemSearch connected libraries for components, variables, and styles.
get_librariesList subscribed and available design libraries for a file.
Security
OAuth grants the server access to your Figma account and files; review the requested scopes and only authorize on trusted clients. As a hosted service, file context is transmitted to Figma's servers.
Figma MCP Server (Official Remote) + Claude Desktop FAQ
Where is the Claude Desktop config file?
Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Figma MCP Server (Official Remote) config there under the "mcpServers" key and restart the client.
Is Figma MCP Server (Official Remote) safe to use with Claude Desktop?
OAuth grants the server access to your Figma account and files; review the requested scopes and only authorize on trusted clients. As a hosted service, file context is transmitted to Figma's servers.
What's the difference between the remote and local Figma MCP servers?
The remote server is hosted by Figma at https://mcp.figma.com/mcp, uses OAuth, and works on all seats/plans with no install. The local server runs inside the Figma desktop app and targets Dev/Full seats on paid plans.
Do I need a paid Figma plan?
The remote server works on all seats and plans (with lower rate limits on Starter/View/Collab seats). The local desktop server requires a Dev or Full seat on a paid plan.
How does authentication work โ is there an API key?
The remote server uses OAuth: you authorize in the browser on first connect, so there's no token to copy. The local server authenticates through your signed-in Figma desktop app.