Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Design - official NVIDIA server

NVIDIA Elements MCP server

Local MCP server started with nve mcp from the NVIDIA Elements CLI, exposing Elements design system component APIs, examples, design tokens, package info and project setup tools to AI assistants. It runs locally from @nvidia-elements/cli (npm) and needs no auth.

Last verified 13 tools4 sources

Install

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

Generic

Snippet
nve project.setup

Tools

api_list
Get list of all available Elements (nve-*) APIs and components.
api_get
Get documentation for 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.
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 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.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • Requires the nve CLI to be installed; nve project.setup auto-configures the MCP server for Cursor, Codex and Claude Code.
  • Also ships MCP prompts (/artifact, /doctor, /create-project, /migrate).

FAQ

What does the NVIDIA Elements MCP server do?

Local MCP server started with nve mcp from the NVIDIA Elements CLI, exposing Elements design system component APIs, examples, design tokens, package info and project setup tools to AI assistants. The vendor documents 13 tools, including api_list, api_get, api_validate and api_imports_get.

How do I add the NVIDIA Elements MCP server to Claude Code?

NVIDIA documents a Claude Code config; copy it from the Claude Code section of this page. Snippets for Codex, Cursor and Generic are there too.

Does the NVIDIA Elements MCP server need authentication?

No. The vendor documents it as needing no auth. Transport: stdio. Status: Unlabelled, last checked October 17, 2026.

Sources

Last verified against 4 NVIDIA pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.