Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
作者提供的说明(英文原文)
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add elements -- npx -y @nvidia-elements/cli mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"elements": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 NVIDIA 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2.2.16)于3天前进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
NVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles.
The @nvidia-elements/cli is a dual-mode command-line tool for the Elements Design System. It provides interactive CLI commands and a Model Context Protocol (MCP) server for AI assistant integration.
This package serves two primary modes:
The best way to get started is to run the install script.
curl -fsSL https://nvidia.github.io/elements/install.sh | bash
On Windows, run the PowerShell installer.
irm https://nvidia.github.io/elements/install.ps1 | iex
For agents and CI, invoke the canonical path directly: $HOME/.nve/bin/nve on macOS and Linux, or $env:LOCALAPPDATA\nve\bin\nve.exe on Windows.
Alternatively you can install with Node.js and npm.
npm install -g @nvidia-elements/cli
| Command | Description |
|---|---|
nve | Show About and help output. |
nve api.list [format] | Get a list of all available Elements (nve-*) APIs and components. |
nve api.get [--format ] | Get documentation for one to five known components or attributes (nve-*). |
nve api.validate [paths..] | Check HTML and JSON from explicit file paths, glob patterns, or standard input (--stdin) using Elements lint rules. |
nve api.imports.get | Get ESM imports for an HTML template using Elements APIs (nve-*). |
nve api.tokens.list [format] [query] | Get available semantic CSS custom properties and design tokens for theming. |
nve api.icons.list [format] | Get available icon names for nve-icon and nve-icon-button. |
nve examples.list [format] | Get available Elements (nve-*) starter templates, patterns, and examples. |
nve examples.get [format] | Get the full template of a known example or pattern by ID. |
nve project.create [cwd] [start] | Create a new starter project. |
nve project.setup [cwd] | Set up or update a project to use Elements. |
nve project.validate [cwd] | Check project configuration and dependencies. |
nve packages.list | Get latest published versions of all Elements packages. |
nve packages.get | Get details for a specific Elements package. |
nve packages.changelogs.get [format] [limit] | Retrieve changelog details by package name. |
nve skills.install [--global] | Install the Elements agent skill in the project or for the current user. |
nve mcp | Start the MCP server. |
| Option | Description |
|---|---|
--help | Show help. |
--version | Show version number. |
--upgrade | Upgrade Elements CLI (nve) to the latest version. |
--debug | Enable debug output for tools. |
The fastest way to configure MCP is with the project.setup command:
nve project.setup
This detects your package manager, configures the MCP server for Cursor, Codex, and Claude Code, and adds Elements core dependencies to the project.
Install to Claude Code by adding the configuration to your .mcp.json file. The file is typically located at ~/.config/claude-code/.mcp.json or %APPDATA%\claude-code\.mcp.json on Windows.
{
"mcpServers": { "nvidia_elements": { "description": "NVIDIA Elements UI Design System (nve-*), custom element schemas, APIs and examples", "command": "nve", "args": ["mcp"] } } }
After adding the configuration, restart Claude Code for the changes to take effect. The Elements MCP tools are then available for use in your conversations.
Install to Cursor with the MCP configuration below.
// .cursor/mcp.json
{ "mcpServers": { "nvidia_elements": { "description": "NVIDIA Elements UI Design System (nve-*), custom element schemas, APIs and examples", "command": "nve", "args": ["mcp"] } } }
Install to Codex with the MCP configuration below.
[mcp_servers.nvidia_elements]
description = "NVIDIA Elements UI Design System (nve-*), custom element schemas, APIs and examples" command = "nve" args = ["mcp"]
| Prompt | Description | Example Prompt |
|---|---|---|
/artifact | Create a standalone Elements UI artifact | /artifact Create an example login form |
/doctor | Verify Elements setup and MCP configuration | /doctor |
/create-project | Create a new Elements starter project | /create-project Create a todo app |
/migrate | Migrate from deprecated Elements APIs | /migrate Migrate this project from deprecated Elements APIs |
Elements provides one elements skill with reference files for artifact creation, setup checks, project integration, and migration. Install the complete directory in the current project:
nve skills.install
This writes .agents/skills/elements/ and .claude/skills/elements/. Add --global to install it for the current user at ~/.agents/skills/elements/ instead. The command replaces existing elements directories at the selected destinations so stale references do not remain.
Alternatively, install the Elements agent skill with the open skills CLI:
npx skills add https://github.com/nvidia/elements --skill elements
This route does not install the Elements CLI or configure the MCP server. Use nve project.setup for complete project setup, and continue to use the CLI or MCP tools for deterministic API lookup and template validation.
| Tool | Description |
|---|---|
api_list | Get list of all available Elements (nve-\*) APIs and components. |
api_get | Get documentation known components or attributes by name (nve-\*). |
api_validate | Checks HTML and JSON files or supplied content with Elements lint rules. |
api_imports_get | Get esm imports for a given HTML template using Elements APIs (nve-\*). |
api_tokens_list | Get available semantic CSS custom properties / design tokens for theming. |
packages_list | Get latest published versions of all Elements packages. |
packages_get | Get details for a specific Elements package. |
packages_changelogs_get | Retrieve changelog details by package name. |
examples_list | Get list of available Elements (nve-\*) patterns and examples. |
examples_get | Get the full template of a known example or pattern by id. |
project_create | Create a new starter project. |
project_validate | Check project for configuration issues and dependencies. |
project_setup | Setup or update a project to use Elements. |