NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-nvidia-elements": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
NVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in design
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
GoPeak — The most comprehensive MCP server for Godot Engine. 95+ tools, LSP, DAP, screenshots.
AI image generation and editing with prompt optimization and quality presets. Powered by Nano Banana
shadcn/ui for Laravel Blade — discover, read and install BlatUI components, blocks and charts.
MCP Security Weekly
Get CVE alerts and security updates for io.github.NVIDIA/elements and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
NVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles.
The repository uses a top-level repository with individual project directories.
Project directories have their own package.json and commands. Run CI and development setup at the root repository level.
Examples of projects include:
/projects/starters - Suite of standardized starter apps for Elements and Patterns/projects/core - Elements library: curated UI maintained by the Elements team/projects/themes - Elements Theme library: provides a set of supported themes for Element based projects/projects/styles - Elements Styles library: provides a set of CSS utilities for layout and typographyTo set up repository dependencies and run the full build, run the following commands at the root of the repository:
The CI pipeline also builds Go starters. Install Go 1.26.x before running the full local CI pipeline.
# install dependencies https://mise.en.dev/getting-started.html
curl https://mise.run | sh
~/.local/bin/mise run setup
If you are coming from development from a different repository, you may need to refresh the repository toolchain with mise. Run mise run install at the root of the project to install the Node.js, pnpm, Vale, Go, Git LFS, and package versions from mise.toml and pnpm-lock.yaml.
If you actively switch between different repositories, run commands through mise exec -- or activate mise in your shell so it switches tools automatically.
Both the top-level repository and each project have a set of standardized npm scripts. To build and test all projects, run mise exec -- pnpm run ci at the root of the repository.
ci: run full build/lint/testci:all: entire CI process: build, lint, unit/lighthouse/visual testsci:reset: clear all caches/dependencies then reinstall dependenciesCommon project scripts include:
dev: run in watch modebuild: run project/library buildtest: run unit teststest:lighthouse: run lighthouse performance teststest:visual: run playwright visual regression teststest:axe: run axe tests for a11yThe available scripts vary by project. Check the project's package.json before running project-specific commands.
For details about the repository build and runtime flow, see the build system documentation.
Before creating a branch or pull request, make a new issue or feature request first so the team can check alignment and avoid duplicate work.
Use a descriptive branch name with the topic/ prefix. Example topic/bug-fix.
git checkout -b topic/bug-fix
After creating your branch, make your source code changes. After you complete them, run mise exec -- pnpm run ci