Figma MCP setup: remote, desktop and your first request

Prepare your own test frame with a distinctive name, a short text line and a known colour. Record its address and expected contents before connecting. This lets you distinguish a successful read of the right object from a result about a similarly named section. This guide proposes a test for your environment; no authenticated Figma account test was performed here.

Choose between remote and desktop

Figma documents https://mcp.figma.com/mcp as its remote endpoint with OAuth authentication. It does not require the desktop app. Enable the desktop server inside the app in Dev Mode; its address is http://127.0.0.1:3845/mcp. Check Figma’s documentation for supported clients. A remote development environment cannot automatically reach your computer through its own loopback address.

A complete VS Code configuration

Open the MCP configuration for the intended VS Code workspace and add this complete structure. If a configuration already exists, add only the entry within servers so existing connections survive. Start the server and complete the offered Figma sign-in. The example contains no credentials. The VS Code guide explains the configuration file in more detail.

{
  "servers": {
    "figma": {
      "type": "http",
      "url": "https://mcp.figma.com/mcp"
    }
  }
}

Use a separate entry with the local address for the desktop route. Give the two connections clear names and keep only the intended connection active during the initial comparison. Otherwise you may not know which source returned a result. The configuration builder uses registry declarations; this provider example is independent of those declarations.

Read one frame and check the result

1. Open the test frame yourself and copy its direct link. Record its name and expected text separately from the later response.

2. Request only the design context for this frame. Figma documents get_design_context for this purpose; inspect the tools your connection actually offers.

3. Compare the object, text and a known property. A screenshot can supplement the visual comparison but does not replace checking returned values.

4. Manually change an unimportant test line in Figma and repeat the request. Record whether the new response contains the updated text.

Diagnose missing selections and oversized responses

The remote route identifies an object through a frame or layer link. The desktop route also supports the selection in the app. Start with an explicit link when a result is missing. If the response is too large, select a smaller frame and compare again. Use the troubleshooting navigator to separate endpoint, authentication and reachability problems.

A successful read does not establish that writes work, that every account file is accessible or that a later implementation will match the design. Test additional tasks separately. The permission planner helps record account access and approvals. The Figma registry search also includes other implementations; a matching product name does not establish that Figma publishes a project.

Common Figma connection questions

Does remote access require the desktop app?

The documented remote route does not. The local desktop server requires the app.

Why does localhost fail inside a container?

Loopback refers to the environment running the calling process. Check which computer actually hosts your MCP client.

Is every connection automatically read-only?

No. Inspect available capabilities and deliberately limit the first test to retrieval.

How do I identify the selected object reliably?

Use a direct frame link and compare it with the intended file. Matching names alone are insufficient evidence.

Provider sources checked on 2 October 2026. The test procedure is an editorial suggestion.

1. Figma: remote server
   Show retrieval command

   curl -s https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/
2. Figma: desktop server
   Show retrieval command

   curl -s https://developers.figma.com/docs/figma-mcp-server/local-server-installation/
3. Figma: Tools and prompts
   Show retrieval command

   curl -s https://developers.figma.com/docs/figma-mcp-server/tools-and-prompts/

All posts