NVIDIA Elements runs on your own machine — the client starts it, so there is no endpoint to ping. 318 installs a week from npm. Last commit 17 Sep 2026.
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
We read the source, 17 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
<nve-steps behavior-select container="${1:condensed}">
<nve-steps-item status="success">${2:Step 1}</nve-steps-item>
spawn(command, args, { stdio: 'inherit' }).on('close', code => process.exit(code ?? 0));
const base = path.join(PROJECTS_ROOT, dir, 'coverage/unit');
const data = eval(`html\`${template}\``); // treat parsed source string as a template literal
await writeFile(join(dist, '.npmrc'), 'registry=https://registry.npmjs.org/');
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add elements -- npx -y @nvidia-elements/cli
{
"mcpServers": {
"elements": {
"args": [
"-y",
"@nvidia-elements/cli"
],
"command": "npx"
}
}
}
[mcp_servers.elements]
command = "npx"
args = ["-y", "@nvidia-elements/cli"]
{
"mcpServers": {
"elements": {
"args": [
"-y",
"@nvidia-elements/cli"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"elements": {
"args": [
"-y",
"@nvidia-elements/cli"
],
"command": "npx"
}
}
}
Design systems, UI prompts, and layout variations for AI coding tools.
MCP Server for Optics Design System documentation and token usage.
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
Figma MCP server for AI agents. 9 tools: design context, variables, screenshots, and FigJam.
Reusable visual design systems for AI coding agents — browse, fetch, and submit styles via MCP.
Design system MCP with 9 tools for component discovery, rendering, and a11y auditing
Give AI agents full read & write access to Figma — 50+ tools for design automation
Answers built from our own checks of this server.