Figma
Files, designs, Dev Mode context
About Figma
Figma is a collaborative product design platform for interface design, prototyping, and developer handoff. Its remote MCP server brings files, designs, and Dev Mode context into assistant workflows so agents can understand visual work and relate it to implementation tasks.
What can you do with the Figma MCP server
- The server can create and modify native content in Figma Design and FigJam, including frames, components, variables, auto layout, stickies, connectors, and shapes.
- The server can capture live web UI and send pages, elements, or flows to Figma Design as editable design layers.
- The server can turn a selected Figma frame into code.
- The server can extract variables, components, and layout data from Figma into an IDE.
- The server can retrieve code resources from Figma Make files and provide them to an LLM as context.
Common use cases
- A developer can paste a link to a selected Figma layer and ask an MCP client to implement that design.
- A developer can capture UI from production, staging, or localhost and add it to a new or existing Figma file.
- A product team can generate code from selected frames when building new flows or iterating on application features.
- A developer can create architecture diagrams or ERDs in a new or existing FigJam file from prompts, code, or structured input.
- A developer can use Code Connect to reuse actual design system components in generated code.
Before you connect
- You must use a code editor or application that supports MCP servers and is listed in Figma's MCP Catalog.
- You must sign in through Figma's OAuth authentication flow to use the remote server.
Connection details
https://mcp.figma.com/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add figma --transport http https://mcp.figma.com/mcpLimitations
- Only clients listed in the Figma MCP Catalog can connect to the remote Figma MCP server.
- Capturing live UI requires the remote server and is currently supported only by select clients.
- An MCP client cannot navigate directly to a selected Figma URL; it extracts the node ID so the server can identify the object.
Frequently asked questions
What is the Figma remote MCP server?
The Figma remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.figma.com/mcp, so AI assistants can connect to it without installing or running anything locally. Figma is a collaborative product design platform for interface design, prototyping, and developer handoff. Its remote MCP server brings files, designs, and Dev Mode context into assistant workflows so agents can understand visual work and relate it to implementation tasks.
How do I connect to the Figma MCP server?
Add the endpoint https://mcp.figma.com/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Figma MCP server require authentication?
Yes. Figma uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Figma MCP server use?
Figma exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
