NVIDIA Elements is a design system and agent-oriented toolkit for building operational interfaces for AI/ML, robotics, and autonomous-vehicle software. Its CLI and MCP tools provide component APIs, design tokens, examples, imports, validation, and setup guidance across several web frameworks.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/NVIDIA/elementsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/nvidia/elements/cli-elements)<a href="https://agentmods.dev/mcp/nvidia/elements/cli-elements"><img src="https://agentmods.dev/badge/mcp/nvidia/elements/cli-elements/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/nvidia/elements/cli-elements"><img src="https://agentmods.dev/badge/mcp/nvidia/elements/cli-elements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
elements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 10 lines scan A 6a82fe95f233
elements is an MCP server published in the GitHub repository NVIDIA/elements (93 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
Framelink MCP for Figma
MCP server "Framelink MCP for Figma" as configured in bartstc/vite-ts-react-template. Launched with pnpm dlx figma-developer-mcp. Needs 2 environment variables to run.
chakra-ui
MCP server "chakra-ui" as configured in bartstc/vite-ts-react-template. Launched with pnpm dlx @chakra-ui/react-mcp.
motionlint
Catch bad animations before they ship. Deterministic motion audit + vision-LLM design review. Runs locally from the motionlint npm package. Needs 4 environment variables to run.
performance_profiler
MCP server "performanceprofiler" as configured in probelabs/visor. Runs ./tools/performance-analyzer.js with node. Needs 2 environment variables to run.
figma-dev-tools
Figma Dev Tools MCP Server v1.4.21 - Bridge Figma designs to code with AI-powered token extraction, framework-agnostic structured data, React/Vue/HTML component generation, asset downloads, XSS security protection, smart hierarchy fixing, SVG inline rende. Runs locally from the figma-dev-tools npm package.