Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
作者提供的说明(英文原文)
Upload, publish and embed 3D models on any website from your agent.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"vectreal": {
"command": "npx",
"args": [
"-y",
"@vctrl/cli",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add vectreal -- npx -y @vctrl/cli mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"vectreal": {
"command": "npx",
"args": [
"-y",
"@vctrl/cli",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"vectreal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vctrl/cli",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 Vectreal 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(3.1.0)于9天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Figma Context MCP, Claude Real Video, Figma MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
The Figma MCP server brings Figma design context directly into your AI workflow.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.