Skip to content
NVIDIA Elements

NVIDIA ElementsMCP Server

by NVIDIA
Released
v2.2.6
Repository Docs npm
Developer Tools

Summary

NVIDIA's official MCP server for the Elements design system — component APIs, design tokens, icons and validated project scaffolding for AI/ML and robotics UIs.

Features

  • Looks up real component APIs and docs instead of letting the agent invent props
  • Validates generated HTML/JSON against the design system's lint rules
  • Serves design tokens and icon names for correct theming
  • Returns the right ES module imports and working example patterns
  • Scaffolds and validates projects, and previews components inline via MCP Apps

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "NVIDIA Elements" tools will be available.
{
  "mcpServers": {
    "nvidia-elements": {
      "command": "npx",
      "args": [
        "-y",
        "@nvidia-elements/cli",
        "mcp"
      ]
    }
  }
}

Description

NVIDIA Elements is NVIDIA's design system: the UI components and design tokens behind its AI/ML, robotics and autonomous-vehicle interfaces. This is its official MCP server, shipped inside the @nvidia-elements/cli package and started with nve mcp.

The problem it solves is the one every design system has with coding agents. Left alone, an agent writes components that look approximately right — a plausible prop that does not exist, a hard-coded colour where a token belongs, an import path from an older major version. The server replaces guessing with lookup across roughly fifteen tools:

  • `api_list` / `api_get` — component APIs and their documentation.
  • `api_validate` — check an HTML or JSON file against the system's linting rules, so the agent can verify its own output rather than assert it.
  • `api_imports_get` — the correct ES module imports for a template.
  • `api_tokens_list` and `api_icons_list` — design tokens for theming and the available icon names.
  • `packages_list` / `packages_get`, `examples_list` / `examples_get` — package metadata and real UI patterns to copy from.
  • `project_create` / `project_validate` — scaffold a project and check it.

It also supports MCP Apps, so components, tokens and icons can be previewed inline in a client that renders them instead of being described in prose.

Install the CLI with the shell one-liner from the docs, the PowerShell equivalent on Windows, or npm install -g @nvidia-elements/cli; then point Claude Code, Cursor or Codex at nve mcp. Published to the MCP registry at version 2.2.6 in September 2026.

Related MCP Servers

MCP: Panda CSS MCP Server

by Panda CSS (Chakra UI)

Official Panda CSS MCP server that exposes your design system - tokens, recipes, patterns, breakpoints and the resolved config - so an agent styles components with real values.

Developer Tools

MCP: NVIDIA CUDA Docs

by NVIDIA

NVIDIA's official remote MCP server for CUDA: grounds a coding agent in first-party CUDA documentation and code samples instead of its training data.

Developer Tools

MCP: Mantine MCP Server

by Mantine

Mantine's official documentation server: gives an agent the component list, per-component docs and the exact props table, so generated React code matches the installed version.

Developer Tools
Browse all MCP servers →