The Figma MCP server brings important context from your Figma Design, Figma Make, and FigJam files right into your development environment, improving your workflows and keeping your code and design components consistent.
Figma has a remote Figma MCP server and a desktop Figma MCP server. Both servers come with many of the same great tools, but there are some minor differences we’ll note below.
The MCP server you choose to use depends mostly on your design and development workflows.
Remote Figma MCP server
Choose the remote Figma MCP server if:
- You primarily use Figma in your web browser.
- You’re unable to use the Figma Desktop app.
- You prefer to copy links to your frames and layers and paste them into your agentic development tool (like VS Code, Claude Code, Cursor, and Windsurf).
- You don’t need to use any tools that are only available with the desktop Figma MCP server.
Figma’s remote MCP server lets you connect directly to an MCP server that’s hosted by Figma. Because the MCP server is hosted by Figma remotely, the remote MCP server is a great option if you prefer to use Figma in the browser, or if you’re unable to use the Figma desktop app.
Share context
The remote Figma MCP server is link-based. That means that you need to provide a URL as context, so your agentic development tool is able to understand what you’re asking it to evaluate.
To provide context with the remote MCP server:
- Copy the file URL from the address bar with nothing selected (this will provide context from the entire Figma Design or Figma Make file).
- Or, right click on a layer and click copy link to selection (this will provide context only from that object).
- Paste the URL into your agentic development tool.
- Type a prompt or use one of the MCP server tools.
Desktop Figma MCP server
Choose the Desktop Figma MCP server if:
- You primarily use the Figma Desktop app
- You prefer to select layers and frames in the desktop app for your agentic development tools to take context from the selection
- The remote MCP server doesn’t support a tool that is important to your workflow
In order to use the Figma Desktop MCP server, you’ll need the Figma desktop app. You can Download the Figma desktop app here. If you already have the desktop app installed, be sure you update to the latest version.
Share context
The Figma Desktop MCP server is selection-based. This means that it can understand the context of your prompts based on the layers you have selected in your Figma Design files. You can still use links to provide context if you prefer.
To provide context to the Figma Desktop MCP server:
- Select any object in your Figma Design file
- Prompt in your agentic development tool
Compare tool availability
After setting up the Figma MCP server, you’ll be able to call various tools from inside of your favorite agentic development tools. These tools will share the context of your selection (when using the desktop MCP server) or the link to a specific file or layer (when using the remote MCP server), with your MCP client.
Most tools are available on both the desktop and remote Figma MCP servers. Currently, some tools may only be available in one of the MCP servers.
Use the tools command in your agentic tool to see the complete list of available tools, and check out our developer documentation for the most up-to-date information.
Connect the MCP server to your editor
Both the Figma remote and desktop MCP servers work with a wide variety of agentic development tools. Follow instructions for your specific editor to connect to the Figma MCP server, either locally or remotely:
| Client | Desktop server support |
Remote server support |
| Amazon Q | ✓ |
|
| Android Studio | ✓ |
✓ |
| Claude Code | ✓ |
✓ |
| Codex by OpenAI | ✓ |
✓ |
| Cursor | ✓ |
✓ |
| Gemini CLI | ✓ |
✓ |
| Kiro | ✓ |
|
| Openhands | ✓ |
|
| Replit |
|
✓ |
| VS Code | ✓ |
✓ |
| Warp | ✓ |
✓ |
Tip: For the latest list of supported editors and clients, check out our MCP Catalog.
Keep in mind that the agentic development tool you use—and the models that power them—are what produce the final code output, not the Figma MCP server. You may want to try multiple MCP client tools to see which produces the best outputs for you.