NVIDIA Elements

io.github.NVIDIAPublished by GitHub account NVIDIAv2.2.16Updated Nov 3, 2026

NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.

The publisher's own server: NVIDIA CUDA Docs

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

NVIDIA Elements MCP server that gives an assistant the Elements UI design system's component APIs, tokens, examples and project tooling.

What you can do
  • Look up Elements (nve-*) components and attributes, and list all available APIs
  • Retrieve design tokens, icon names and ESM imports for an HTML template
  • Browse and fetch example templates and patterns by ID
  • Validate HTML and JSON against Elements lint rules
  • Check package versions and changelogs
  • Create starter projects, set up or validate a project's Elements configuration
When to use it
Use it when building or maintaining web interfaces with NVIDIA's Elements design system and you want the assistant to work from accurate component docs, tokens and templates instead of guessing. It also helps with migrating away from deprecated Elements APIs or scaffolding a new Elements project.
Requirements
Runs locally over stdio via npx from the npm package @nvidia-elements/cli, or from a globally installed nve command; Node.js and npm are needed for that route. The README also offers a curl/PowerShell install script. No accounts, API keys or environment variables are declared.
Before you install
The README's install instructions pipe a remote script from the project site into a shell, which executes third-party code; the npm install route avoids that. Project setup and skill installation write configuration and files into your project, and skill installation replaces existing elements skill directories at the chosen destination. Project creation and setup modify the working directory.

Installation

In SourceWeft

  1. Open NVIDIA Elements in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@nvidia-elements/cli

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.

Purpose

This package serves two primary modes:

  1. Interactive CLI (nve command) - Command-line interface with interactive prompts for:

    • Component API discovery and search
    • Example template browsing and searching
    • Template linting and validation
    • Project scaffolding and health checks
    • Changelog and version information
    • Design token access
    • Icon name lookup
    • Bundled agent skill access

  2. MCP Server (nve mcp command) - Model Context Protocol server that:

    • Exposes MCP-supported tools to AI assistants (Claude, Cursor, etc.)
    • Provides context-specific prompts for common tasks
    • Enables AI-assisted development with Elements components
    • Integrates Elements knowledge directly into AI workflows

Getting Started

The best way to get started is to run the install script.

shell
curl -fsSL https://nvidia.github.io/elements/install.sh | bash

On Windows, run the PowerShell installer.

powershell
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.

shell
npm install -g @nvidia-elements/cli

Usage

CommandDescription
nveShow About and help output.
nve api.list [format]Get a list of all available Elements (nve-*) APIs and components.
nve api.get <names..> [--format <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 <template>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 <id> [format]Get the full template of a known example or pattern by ID.
nve project.create <type> [cwd] [start]Create a new starter project.
nve project.setup [cwd]Set up or update a project to use Elements.
nve project.validate <type> [cwd]Check project configuration and dependencies.
nve packages.listGet latest published versions of all Elements packages.
nve packages.get <name>Get details for a specific Elements package.
nve packages.changelogs.get <name> [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 mcpStart the MCP server.

Global Options

OptionDescription
--helpShow help.
--versionShow version number.
--upgradeUpgrade Elements CLI (nve) to the latest version.
--debugEnable debug output for tools.

MCP

Quick Setup

The fastest way to configure MCP is with the project.setup command:

shell
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.

Claude Code

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.

json
{  "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.

Cursor

Install to Cursor with the MCP configuration below.

json
// .cursor/mcp.json{  "mcpServers": {    "nvidia_elements": {      "description": "NVIDIA Elements UI Design System (nve-*), custom element schemas, APIs and examples",      "command": "nve",      "args": ["mcp"]    }  }}

Codex

Install to Codex with the MCP configuration below.

toml
[mcp_servers.nvidia_elements]description = "NVIDIA Elements UI Design System (nve-*), custom element schemas, APIs and examples"command = "nve"args = ["mcp"]

Prompts

PromptDescriptionExample Prompt
/artifactCreate a standalone Elements UI artifact/artifact Create an example login form
/doctorVerify Elements setup and MCP configuration/doctor
/create-projectCreate a new Elements starter project/create-project Create a todo app
/migrateMigrate from deprecated Elements APIs/migrate Migrate this project from deprecated Elements APIs

NVIDIA Elements Skill

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:

shell
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:

shell
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.

MCP Tools

ToolDescription
api_listGet list of all available Elements (nve-*) APIs and components.
api_getGet documentation known components or attributes by name (nve-*).
api_validateChecks HTML and JSON files or supplied content with Elements lint rules.
api_imports_getGet esm imports for a given HTML template using Elements APIs (nve-*).
api_tokens_listGet available semantic CSS custom properties / design tokens for theming.
packages_listGet latest published versions of all Elements packages.
packages_getGet details for a specific Elements package.
packages_changelogs_getRetrieve changelog details by package name.
examples_listGet list of available Elements (nve-*) patterns and examples.
examples_getGet the full template of a known example or pattern by id.
project_createCreate a new starter project.
project_validateCheck project for configuration issues and dependencies.
project_setupSetup or update a project to use Elements.

Links

Source: projects/cli/README.md at commit 4cb13a1

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

14
  1. v2.2.16LatestNov 3, 2026
  2. v2.2.15Oct 30, 2026
  3. v2.2.14Oct 29, 2026
  4. v2.2.13Oct 25, 2026
  5. v2.2.12Oct 22, 2026
  6. v2.2.11Oct 21, 2026
  7. v2.2.10Oct 20, 2026
  8. v2.2.9Oct 9, 2026
  9. v2.2.8Oct 1, 2026
  10. v2.2.7Sep 30, 2026
  11. v2.2.6Sep 25, 2026
  12. v2.2.5Sep 24, 2026
  13. v2.2.4Sep 22, 2026
  14. v2.2.3Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Nvidia integrations

NVIDIA CUDA Docs

com.nvidia.ngc.nsight.copilot.apiOfficial publisher

A remote MCP endpoint that lets AI coding agents search NVIDIA CUDA documentation and code samples.

Streamable HTTPWeb executableAuth
Knowledge & MemoryCredential requiredOct 25, 2026

Nvidia Nim Mcp

Published by GitHub account david-eve-za

Local MCP server that connects an assistant to NVIDIA NIM models for chat, text generation, embeddings, reranking, image generation and vision tasks.

STDIODesktop only
Media & DesignNot validated yetOct 24, 2026

NVIDIA NemoClaw CKG

Published by GitHub account Yarmoluk

A knowledge-graph server for NVIDIA NemoClaw that lets an assistant answer questions, trace prerequisites and verify sources across 55 typed concept nodes.

Streamable HTTPWeb executable
Knowledge & Memory8 toolsOct 27, 2026

NVIDIA AI CKG

Published by GitHub account Yarmoluk

Provides an assistant with NVIDIA AI knowledge graphs spanning 20 domains, with provenance hashing and token-efficient retrieval.

Streamable HTTPWeb executable
Knowledge & Memory9 toolsOct 24, 2026