Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Upload, publish and embed 3D models on any website from your agent.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"vectreal": {
"command": "npx",
"args": [
"-y",
"@vctrl/cli",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add vectreal -- npx -y @vctrl/cli mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vectreal": {
"command": "npx",
"args": [
"-y",
"@vctrl/cli",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"vectreal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vctrl/cli",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account Vectreal, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (3.1.0) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The Vectreal command line: sign in once, then let a terminal or an agent act for you in the organization you chose.
Run it with npx, or install it globally to get the vectreal command:
npx -y @vctrl/cli login
npm install -g @vctrl/cli
Setup for Claude Code, Cursor and VS Code is in the agents docs.
| Command | What it does | |
|---|---|---|
vectreal login [--origin ] [--no-browser] | Signs in through the browser and keeps the session in the OS keychain. Remembers the origin for later commands. | |
vectreal whoami [--json] | Shows the user, organization, role and scopes the session acts as. | |
| `vectreal init [--project \ | --create ]` | Links the current directory to a project by writing .vectreal/project.json. |
vectreal logout | Ends the session on the server and forgets it here. | |
vectreal mcp | Serves the Vectreal tools to an agent over stdio (MCP) until the agent closes the stream. | |
vectreal mcp install [--origin ] | Registers that server in the current directory's .mcp.json, launched the way this CLI was. |
The origin is --origin, then VECTREAL_ORIGIN, then the last one signed in to, then https://vectreal.com. Plain http is allowed on localhost only.
vectreal mcp gives an agent these tools:
| Tool | Does |
|---|---|
search_docs, read_doc | Search and read the Vectreal docs. No sign-in needed. |
whoami, list_projects, create_project, list_scenes | Who the session is, and the organization's projects and scenes. |
create_scene_from_file | Uploads a local GLB as a draft scene, as it is. |
describe_model | A local GLB's size, meshes, materials and animation clips, and where the viewer places it, without rendering it. |
get_scene_settings, update_scene_settings | Read every settings section; change lighting, environment, controls, bounds, shadows and presentation. Lighting supersedes environment and shadows once a scene has it. |
publish_scene, unpublish_scene | Compress a local GLB as the publisher does (Draco, KTX2) and publish it; take a scene offline. |
get_embed_snippet | The snippet and preview URL for a published scene, creating an embed key and allowing domains when asked. |
Tools that take projectId default to the project vectreal init linked. The server finds that project in CLAUDE_PROJECT_DIR when the agent sets it, else in the directory it was started from. It signs in with the stored session, so run vectreal login first; a tool called without one says so.
To register it with Claude Code, run this in the project directory:
claude mcp add vectreal -- npx -y @vctrl/cli mcp
Or let the CLI write the entry into the current directory's .mcp.json:
npx -y @vctrl/cli mcp install
Run from npx, the entry it writes is npx -y @vctrl/cli mcp, so .mcp.json can be committed. Run from a checkout of this repository, it names paths on that machine instead.
The server is also listed in the MCP Registry as io.github.Vectreal/vectreal.
Results go to stdout, as JSON with --json. Everything else goes to stderr.
| Code | Meaning |
|---|---|
| 0 | Done |
| 1 | Failed |
| 2 | Wrong usage |
| 3 | Not signed in, or the server no longer accepts the session: run vectreal login |
In the OS keychain (macOS Keychain, Windows Credential Manager, Secret Service on Linux), one entry per origin. Where the keychain cannot be used, as on a headless Linux box with no Secret Service, the session goes to $XDG_CONFIG_HOME/vectreal/credentials.json (default ~/.config/vectreal) instead, and each command that does so says it on stderr. On macOS and Linux that file is readable only by you; on Windows it relies on your profile folder's permissions.
Register the CLI's OAuth client on the local Supabase stack once, then point the CLI at the dev server:
pnpm nx run vectreal-platform:supabase-register-cli-client
pnpm -s vectreal login --origin http://localhost:4200
From a checkout, use pnpm's -s: without it, pnpm prints its own banner to stdout before the CLI does, which breaks anything reading --json output.