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)
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
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": {
"elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add elements -- npx -y @nvidia-elements/cli mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/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": {
"elements": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nvidia-elements/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 NVIDIA, 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 (2.2.16) reached the registry 3 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.
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. |