Connect Figma (desktop MCP) to Gemini CLI
Figma's local MCP server, served by the desktop app. Gives agents design context, variables and code-connect data for the selected frame.
MCP serverOfficialChecked 2026-11-16
Before you start
- Gemini CLI installed (see its MCP documentation (opens in a new tab)).
- Figma (desktop MCP) is available on macOS and Windows. Keep its desktop app open while you work.
- Needs the Figma desktop app with a Dev or Full seat on a paid plan, and the desktop MCP server enabled.
Step 1: Add Figma (desktop MCP) to Gemini CLI
Add it from the terminal
Run this in your project folder. It saves the server to the project's
.gemini/settings.json.Terminal gemini mcp add --transport http figma-desktop http://127.0.0.1:3845/mcpOr edit the config file
Add this to
.gemini/settings.jsonin your project, or to~/.gemini/settings.jsonto use it in every project..gemini/settings.json { "mcpServers": { "figma-desktop": { "httpUrl": "http://127.0.0.1:3845/mcp" } } }Good to know- The desktop app must be open for the server to respond.
Step 2: Check it's connected
Terminal gemini mcp listIn a Gemini CLI session, run
/mcpto see each server, its status and its tools.Step 3: Try a first request
Ask Gemini CLI something that only works with Figma (desktop MCP) connected:
Say to Gemini CLI Get the design context for the frame I have selected in Figma and list the components it uses.
If it doesn't work
- Since June 2026, Gemini CLI works with a paid Gemini API key or an enterprise licence. If you signed in with a personal Google account, use Google Antigravity instead.
gemini mcp addsaves to the project's.gemini/settings.jsonby default. Add--scope userto save it to~/.gemini/settings.jsonfor every project.- Local servers only show as connected in folders you trust. Run
gemini trustin the project folder. - Gemini CLI hides environment variables that look like secrets from servers unless the server's
envblock lists them.






