Connect Figma (remote MCP) to Gemini CLI
Figma's hosted MCP server with design context and beta canvas writes. Available on all plans, with tight call limits on Starter, View and Collab seats.
MCP serverOfficialChecked 2026-11-16
Before you start
- Gemini CLI installed (see its MCP documentation (opens in a new tab)).
- Figma (remote MCP) is available on macOS, Windows, Linux and the web.
- Starter plan and View/Collab seats get 6 tool calls a month; Dev/Full seats on paid plans get 200 a day.
Step 1: Add Figma (remote 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-remote https://mcp.figma.com/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-remote": { "httpUrl": "https://mcp.figma.com/mcp" } } }Good to know- The first time, run
/mcp auth figma-remotein a session to sign in.
- The first time, run
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 (remote MCP) connected:
Say to Gemini CLI Here's a link to a Figma frame: <paste link>. Summarise its layout and the variables 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.






