Figma-Context-MCP server in Continue.dev Figma data in your open-source assistant.
A short YAML block in config.yaml — or a drop-in file under .continue/mcpServers/ — connects Continue's agent mode to your Figma files via the figma-developer-mcp package.
Continue.dev is the open-source assistant that lets you bring your own models, and since agent mode landed it speaks MCP like the rest of the field. Figma-Context-MCP (github.com/glips/figma-context-mcp, 15.1k stars) is one of the highest-value servers to add: it hands the agent real Figma layout and component data so a linked frame becomes implementable structure, not a vibe.
The one thing that makes Continue different from every JSON-based client on this list: configuration is YAML. Indentation is syntax, and a snippet copied from a Cursor or Claude Desktop tutorial won't paste in directly.
Pick your scope: config.yaml or a drop-in file
Continue reads MCP servers from two places. Your global ~/.continue/config.yaml applies everywhere — right for a personal token and a server you use across projects. Alternatively, drop a standalone YAML file into .continue/mcpServers/ inside a repo and the server loads only for that project; that file can be committed so teammates inherit the setup (minus secrets).
Before either, generate a Figma personal access token under Figma Settings > Security > Personal access tokens. It needs read access to the files you'll be referencing.
The config
Note the structure: mcpServers in Continue's YAML is a list of named entries, not an object keyed by name. The package is figma-developer-mcp from npm, run over stdio:
mcpServers:
- name: figma-context
command: npx
args:
- "-y"
- figma-developer-mcp
- "--stdio"
env:
FIGMA_API_KEY: YOUR_FIGMA_TOKENReload and verify
Continue generally hot-reloads config.yaml on save, but when in doubt reload the extension (Developer: Reload Window in VS Code) so there's no stale state. Open the Continue sidebar in agent mode and check the tools list — figma-context should appear with tools for fetching file data and downloading image assets. MCP tools only run in agent mode; in plain chat or edit mode the server sits idle by design.
Test with a selection link from Figma (right-click a frame > Copy link to selection) and ask the agent to describe or implement that frame. The node ID in a selection link keeps the fetched payload to just that subtree — fetching a whole design file is the quickest way to flood your model's context.
Troubleshooting in Continue.dev
YAML errors dominate here: a tab character instead of spaces, or a mis-indented env block, silently drops the server. If figma-context is missing from the tools list, run your config.yaml through a YAML linter before suspecting anything else. Second suspect is the runtime — Continue spawns the server with npx, so VS Code needs your Node environment; launching VS Code from a terminal fixes most nvm-related misses.
If tools appear but calls fail, it's the token: expired, or pointing at a Figma file your account can't open. And if you migrated from Continue's older config.json era, make sure you're editing config.yaml — the JSON file is legacy, and edits there won't register on current versions.
Where this server sits
You can see Figma-Context-MCP's probed tool list on its live Loomal listing at https://loomal.ai/marketplace/figma-context-mcp. It leads the design tools category by a wide margin, and since Continue lets you swap models freely, it's a good server for comparing how different models handle the same structured design data.
FAQ
How do I install Figma-Context-MCP in Continue.dev?
Add an mcpServers list entry to ~/.continue/config.yaml — name figma-context, command npx, args -y figma-developer-mcp --stdio, and FIGMA_API_KEY under env — or drop the same block as a file in .continue/mcpServers/ for project scope. Reload the extension and the tools appear in agent mode.
Where is Continue.dev's MCP configuration?
Globally in ~/.continue/config.yaml, or per-project as individual YAML files under .continue/mcpServers/ in the repo. Both are YAML, not JSON — config.json is the deprecated older format and current versions ignore MCP entries placed there.
The server doesn't show up in Continue after setup — what do I check?
Lint the YAML first; indentation mistakes are the leading cause and fail silently. Then confirm you're in agent mode, since MCP tools don't surface in chat or edit modes. Finally check that npx resolves in VS Code's environment by launching VS Code from your terminal.
Can my team share this setup?
Yes — commit a YAML file under .continue/mcpServers/ in the repo so everyone loads the server on clone. Keep the FIGMA_API_KEY out of the committed file; each developer should supply their own token, since Figma personal access tokens carry the holder's full file access.
Browse more MCP servers for Continue.dev.
Check a server's live tool list before you write the YAML.