NVIDIA Elements MCP: Component APIs for Any Framework

What is NVIDIA Elements MCP?

It is the mcp subcommand of @nvidia-elements/cli, a dual-mode package that also ships the nve command line tool. Running nve mcp starts a local server that exposes the same component data the CLI already reads, so an agent gets a real API shape instead of an invented one.

What the tools cover

• api_list and api_get return real documentation for named nve- components and attributes, up to five at a time.
• api_validate checks HTML or JSON content against Elements lint rules, from paths, globs or piped input.
• api_imports_get returns the ESM imports an HTML template needs for the nve- elements it already uses.
• api_tokens_list returns the semantic CSS custom properties behind theming, searchable by a query.
• examples_list and examples_get return known starter templates and patterns by id.
• packages_list, packages_get and packages_changelogs_get return current package versions and release notes.
• project_create, project_validate and project_setup scaffold, check and configure a project for Elements.

Framework reach

The nve- custom elements are Web Components, so they run the same in React, Angular, Vue, Svelte, Lit, plain HTML and server-rendered templates. The MCP tools return the same component data regardless of which framework the calling project uses.

Who NVIDIA Elements MCP is for

Best for

• Teams building AI or ML tooling, robotics consoles or autonomous vehicle interfaces who want one component set across several frontend stacks.
• Agents that need a verified token name or import line instead of inventing CSS or markup for an nve- element.
• Multi-framework codebases, since the same component APIs and tokens apply whether a page is React, Svelte, Vue or plain HTML.

Not for

• When a project is already standardized on shadcn/ui components and blocks for React, Vue or Svelte specifically, the community shadcn/ui MCP Server is the better fit for that stack.
• When the goal is reading Web Component APIs and design tokens from any Custom Elements Manifest rather than the nve- components specifically, HELiXiR MCP is the better fit for that broader reach.
• When the reference needed is Apple's own Human Interface Guidelines and SwiftUI mappings rather than NVIDIA's own component tokens, the Apple HIG tokens server is the better fit for that platform.
• When the component set needed is a vendor's own 66-component CSS library with vt- class names rather than NVIDIA's nve- Web Components, Veritheme MCP Server is the better fit for that library.

Connect NVIDIA Elements MCP: Component APIs for Any Framework to your AI client

npm install -g @nvidia-elements/cli
nve project.setup

1. Install the CLI

   Run npm install -g @nvidia-elements/cli, or the shell installer at nvidia.github.io/elements/install.sh, to put the nve command on PATH.

2. Auto-configure your client

   Run nve project.setup in your project. It detects the package manager and configures the MCP server for Cursor, Codex and Claude Code in one pass, plus adds the Elements core dependency.

3. Or add it by hand

   Add the config above to your client's MCP settings, with command nve and args mcp.

4. Restart and check

   Restart your client and ask it to run the doctor prompt, which confirms the Elements MCP tools and prompts are registered.

Client configuration

{
  "mcpServers": {
    "nvidia_elements": {
      "command": "nve",
      "args": ["mcp"]
    }
  }
}

What you can do with it

• Framework-agnostic Web ComponentsThe nve- elements run unchanged in React, Angular, Vue, Svelte, Lit, plain HTML and server-rendered templates.
• Real component lookup, not a guessapi_get returns documented props and slots for a named component instead of an agent inventing markup.
• Lint before it shipsapi_validate runs Elements' own rules over HTML or JSON from paths, globs or piped input.
• Design tokens on demandapi_tokens_list returns the semantic CSS custom properties behind theming, searchable by name.
• Starter templates includedexamples_list and examples_get return known patterns and starter templates by id, not a blank page.
• Package and changelog awarenesspackages_list, packages_get and packages_changelogs_get keep an agent's suggestions aligned with the current release.
• One command configures multiple clientsnve project.setup detects the package manager and wires the MCP server into Cursor, Codex and other supported editors together.
• Reusable prompts for common tasksartifact, doctor, create-project and migrate wrap frequent requests so an agent does not reconstruct them each time.

Tools it exposes

Frequently asked questions