How to Fix the Figma MCP Server Startup Error

Figma MCP startup errors usually come from selecting the wrong server, using an unsupported client configuration, missing authorization, or starting the desktop server without an active Figma file. First identify the endpoint in your MCP configuration:

• https://mcp.figma.com/mcp means the Figma-hosted remote server.
• http://127.0.0.1:3845/mcp means the local desktop server.

Follow the matching branch below, then restart or refresh your MCP client so it reloads the server’s tool list.

1. Choose the correct Figma MCP server

Diagnostic point	Remote server	Desktop server
Runs at	Figma’s hosted service	Your Figma desktop app
Endpoint	https://mcp.figma.com/mcp	http://127.0.0.1:3845/mcp
Desktop app required	No	Yes
Setup	Supported client plus Figma authorization	Open a Design file, select Dev Mode, enable MCP
Recommended use	Most users and broadest feature set	Specific organization or enterprise requirements

Figma strongly recommends the remote server because it connects directly to the hosted endpoint without requiring the desktop app. Figma for Government supports the desktop server only. See the Figma MCP introduction for the current product scope.

2. Fix a remote-server startup error

Check client support

Figma says only clients in its supported client catalog can connect to the remote server. Confirm that your MCP client is listed before debugging configuration. A client developer who is not listed must use Figma’s documented waitlist process.

Use the remote endpoint and HTTP transport

Your client must support HTTP or Streamable HTTP MCP connections. A generic configuration looks like this:

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

Follow your client’s authorization flow after saving the configuration. In VS Code, Figma’s documented flow uses an mcp.json entry with the remote URL and HTTP type, then the client’s Start action and Allow Access in Figma. Use the official remote-server setup for client-specific fields.

Confirm authorization

1. Start the configured Figma server from the MCP client.
2. Complete the Figma sign-in and consent screen in the browser.
3. Return to the client and confirm the server status says connected or authorized.
4. Open a Figma file that your account can access and invoke a Figma tool.

If the browser authorization succeeds but the client remains disconnected, remove the stale server entry, add it again, and repeat authorization. Also verify that the URL has no trailing typo, quotation mark, or copied whitespace.

Codex-specific checks

Figma’s Codex setup includes installing its Figma plugin and authorizing access. If the plugin or tools do not appear, ask the Codex administrator whether third-party plugins are allowed and whether new tools require approval. Use Figma’s Codex setup instructions for the current UI.

3. Fix a desktop-server startup error

The desktop endpoint works only while the Figma desktop app and an active Design file are ready.

1. Update and open the Figma desktop app.
2. Open or create a Figma Design file.
3. Switch to Dev Mode. Figma documents Shift+D as the shortcut.
4. Open the inspect panel’s MCP section.
5. Enable the desktop MCP server and wait for Figma to report that it is running.
6. Configure the client with this exact URL:

{
  "mcpServers": {
    "figma-desktop": {
      "type": "http",
      "url": "http://127.0.0.1:3845/mcp"
    }
  }
}

7. Start or refresh the MCP connection in your client.
8. Keep the Figma app, file, and Dev Mode active while using the tools.

Figma’s desktop-server instructions describe the required app state. A browser-only Figma session cannot provide this local endpoint.

4. When the server connects but tools are missing

MCP clients read the available tools at startup. If you changed the URL or enabled the desktop server after the client started, restart or refresh the client so it reads the new tool list.

Check for a configuration conflict. If both remote and desktop servers are present, the client may connect to the desktop server and omit tools that are available only remotely, including use_figma and generate_figma_design. Temporarily disable one entry, reconnect, and check which endpoint the client selected.

Figma’s troubleshooting guidance also recommends confirming that the desktop server is enabled, the Figma app is running, and the file is open, then restarting both Figma and the IDE. See Tools aren’t loading or connection lost.

5. Troubleshooting common errors

Symptom	Likely cause	Fix
Connection refused on port 3845	Desktop server is disabled, Figma is closed, or no Design file is active	Open the desktop app and file, select Dev Mode, enable MCP, then reconnect.
Remote server never authorizes	Unsupported client, wrong URL, or incomplete consent	Use a listed client, set https://mcp.figma.com/mcp, and complete Figma authorization.
Connected status but no Figma tools	Client cached an old tool list or selected the other server	Restart or refresh the client and disable the conflicting server entry.
Only some tools appear	Desktop mode does not expose remote-only tools	Connect to the remote endpoint or verify which server is selected.
Tools disappear after closing Figma	The local desktop server depends on the running app	Reopen Figma, the Design file, and Dev Mode; keep them active.
“We’re having trouble connecting to the model provider”	The AI assistant cannot reach its model or timed out	Retry after checking the assistant’s model connection. This message does not prove that Figma MCP is down.
Authorization opens the wrong account	Browser session is signed into another Figma account	Sign out or use a separate browser profile, then authorize the intended account.

6. A repeatable diagnostic checklist

• Record the exact error text, operating system, MCP client, and selected endpoint.
• Use only one Figma server entry while diagnosing.
• For remote: verify client support, URL, HTTP transport, and authorization.
• For desktop: verify Figma desktop, an open Design file, Dev Mode, and the enabled server.
• Restart Figma and the IDE after changing configuration.
• Confirm the client’s tool list after reconnecting.
• Separate model-provider timeouts from MCP transport failures.

7. Reliability and performance considerations

The remote server removes the desktop app and local port from the failure path, which is why Figma recommends it for most users. The desktop server adds a dependency on the running app, active file, Dev Mode, and local network permissions. For teams using desktop mode, make the app/file state part of the startup checklist.

Tool discovery happens when the client starts. Restarting after configuration changes prevents stale capabilities from being mistaken for a server failure. If a request takes a long time, determine whether the timeout comes from the AI model provider or from the MCP connection before changing Figma settings.

Or skip the browser setup

If your workflow needs website screenshots while you diagnose an MCP integration, ScreenshotNeo provides a single screenshot API request. Its cleanup step accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result. It also provides an MCP server with take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.

See the ScreenshotNeo API documentation for all options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

There are 1,000 free screenshots each month with no card. Paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

FAQ

Which Figma MCP server should I use?

Use the remote server for most setups. Use desktop mode when your organization requires the Figma desktop app or when using Figma for Government.

Can I use both servers?

You can configure both, but the client may select the desktop server and hide remote-only tools. Keep one enabled while diagnosing missing tools.

Does the desktop server work with a Figma browser tab?

No. It requires the Figma desktop app with an active Design file, Dev Mode, and the MCP server enabled.

Why did tools vanish after I edited the configuration?

Most clients read tools at startup. Restart or refresh the client after changing the server URL or enabling desktop MCP.

Is a model-provider error the same as an Figma MCP error?

No. Figma says that message usually concerns the assistant’s model connection or a timeout. Retry or wait for the model connection to recover.