# NVIDIA Elements

Connects the NVIDIA Elements design system to coding assistants. Helps generate and validate UI interfaces for robotics and autonomous vehicles.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 106
- Author: NVIDIA
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/NVIDIA/elements/tree/HEAD/projects/cli
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/nvidia-elements

## What it does

The `@nvidia-elements/cli` package operates in two modes. It acts as an interactive terminal command and runs as an MCP server via `nve mcp`. This gives coding agents direct access to the Elements design system.

The server exposes `nve-*` custom elements schemas. Assistants can fetch component APIs, retrieve icons, or test templates against design rules via `api.validate`.

Running `nve project.setup` automates MCP configuration in Claude Code and Cursor. In headless CI environments, agents must call `$HOME/.nve/bin/nve` directly. Otherwise, the command will fail.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add elements -- npx -y @nvidia-elements/cli
```

### Codex

**Platform CLI**
```bash
codex mcp add cli -- npx -y @nvidia-elements/cli
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "cli": {
            "command": "npx",
            "args": [
                "-y",
                "@nvidia-elements/cli"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "cli": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@nvidia-elements/cli"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add cli npx -y @nvidia-elements/cli
```

## When to use it
- inspect documentation for nve-* UI components and attributes
- validate templates and HTML files against design system rules
- look up semantic tokens and custom CSS properties for styling
- scaffold initial project structures using Elements starters

## Example prompts
- Check if my markup follows Elements guidelines with api.validate
- Find the documentation and properties for nve-card
- Generate a sample dashboard screen using /artifact

## Similar
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74559
- [tldraw](https://affpapa.org/en/nevibecode/mcp/tldraw.md) — MCP server · ★ 51091
- [Figma-Context-MCP](https://affpapa.org/en/nevibecode/mcp/figma-context-mcp.md) — MCP server · ★ 16062
- [mcp-server-chart](https://affpapa.org/en/nevibecode/mcp/mcp-server-chart.md) — MCP server · ★ 4402
- [Dembrandt](https://affpapa.org/en/nevibecode/mcp/dembrandt.md) — MCP server · ★ 3821
- [RevoGrid DataGrid MCP Pro](https://affpapa.org/en/nevibecode/mcp/revogrid-datagrid-mcp-pro.md) — MCP server · ★ 3450

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md