Maps & transport · Local MCP server
NVIDIA Elements
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.NVIDIA/elements- Version
- 2.2.8
- Status
- Active
- Category
- maps & transport
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- NVIDIA (GitHub)
- Website
- nvidia.github.io/elements/docs/mcp/
- Repository
- github.com/NVIDIA/elements (folder projects/cli)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @nvidia-elements/cli | 2.2.8 | stdio |
How to connect NVIDIA Elements
NVIDIA Elements runs locally from a Node.js package published to the npm registry: @nvidia-elements/cli version 2.2.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @nvidia-elements/cli@2.2.8.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli@2.2.8"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, nvidia.github.io, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More maps & transport servers
| Server | Runs |
|---|---|
| NominatimNominatim MCP — wraps OpenStreetMap Nominatim geocoding API (free, no auth) | Remote · HTTP |
| Nominatim MCPOpenStreetMap Nominatim geocoding and reverse geocoding (merged). | Local · stdio |
| Ns MCPNS Dutch Railways API: departures, stations, journeys, disruptions, fares. | Local · stdio |
| NTNU Courses (unofficial)Unofficial NTNU course data: search, timetables, grades, course info, and exam logistics. | Remote · HTTP |
| Ny DmvNew York State DMV MCP — registered vehicles and EV adoption by county/ZIP/make,. | Remote · HTTP |
| NYC FHV Intelligence APIReal-time NYC TLC for-hire vehicle license verification and renewal-window lead lookups via MCP. | Local · stdio |
| Ocean SchedulesCompare ocean carrier sailing schedules, transit times, and on-time reliability before you book. | Remote · HTTP |
| OeBB (Austrian Railways)OeBB (Austrian Railways) train data: stations, departures, connections, service alerts. | Local · stdio |