A
licenseNot graded
qualityD
maintenanceEnables AI assistants to read, inspect, and manipulate OpenUSD 3D scenes, including scene graph traversal, property querying, mesh export, and variant switching.
10
MIT
NVIDIA USDCode MCP Server
by ishandotsh
Provides access to NVIDIA USDCode via the NVIDIA Integrate API for Isaac Sim scripting assistance, USD guidance, Python code snippets, and API usage help
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NVIDIA USDCode MCP ServerHow do I create a simple robot arm in Isaac Sim using USD?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
nvidia-usdcode-mcp-server
A minimal MCP server that exposes a single tool backed by NVIDIA USDCode via the NVIDIA Integrate API. Great for Isaac Sim scripting tips, USD, Python snippets, and API usage.
Requirements
Node.js 18+
An NVIDIA API key in
NVIDIA_API_KEY, get it from here https://build.nvidia.com/nvidia/usdcode
You can place it in a local .env file (loaded automatically) or export it in your shell.
Related MCP server: Isaac Sim MCP Server
Quickstart
Dependencies are already vendored in this workspace. If you need to reinstall:
npm ciornpm install
Build
npm run build
Outputs to dist/.
Run (standalone)
npm start(after building)Or directly:
node --enable-source-maps dist/server.js
The server speaks MCP over stdio and is intended to be launched by an MCP-capable client.
Use with Claude Desktop
Add an entry to your ~/.claude/config.json:
{
"mcpServers": {
"usdcode": {
"command": "node",
"args": ["dist/server.js"],
"env": { "NVIDIA_API_KEY": "YOUR_KEY" }, // if you didn't add .env to this project
"disabled": false
}
}
}Use with OpenAI Codex
Add an entry to your ~/.codex/config.toml:
[mcp_servers.usdcode]
command = "node"
args = ["/absolute/path/to/mcp-usdcode/dist/server.js"]
env = { "NVIDIA_API_KEY" = "value" }Tool Info
name:
get_usdcode_helpdescription: Ask NVIDIA USDCode for help.
params:
question(string, required): Your prompt or question.temperature(number, optional, default 0.1)top_p(number, optional, default 1)max_tokens(integer, optional, default 1024)expert_type(string, optional, default "auto")
Returns a single text message with the model’s reply.
Available Tools
1 toolget_usdcode_helpC
Ask NVIDIA USDCode for help (Isaac Sim scripting, USD, Python/API tips).
Parameters: temperature (0-1, default 0.1), top_p (<=1, default 1), max_tokens (1-2048, default 1024), expert_type (auto|knowledge|code|helperfunction; default auto), stream (boolean; default false). Avoid changing temperature and top_p together.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes | Your prompt or question | |
| temperature | No | Sampling temperature (0-1). Default: 0.1 | |
| top_p | No | Top-p nucleus sampling mass (<=1). Default: 1 | |
| max_tokens | No | Max tokens to generate (1-2048). Default: 1024 | |
| expert_type | No | Expert to use: auto, knowledge, code, or helperfunction. Default: auto | |
| stream | No | Stream partial deltas via SSE. Default: false |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the tool is for 'help' and lists parameter defaults, it doesn't describe what kind of response to expect, whether it's a one-time answer or ongoing conversation, rate limits, authentication needs, or error handling. The description provides minimal behavioral context beyond basic parameter information.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized with two sentences. The first sentence states the purpose clearly, and the second provides parameter context. There's no wasted text, though the parameter listing could be more integrated rather than appearing as a separate bullet-like section.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what format the help response will take, whether it's conversational or single-answer, how to interpret different expert_type selections, or what happens when parameters conflict. The description leaves too many behavioral questions unanswered for a tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents all 6 parameters. The description adds only one piece of semantic information: 'Avoid changing temperature and top_p together.' This provides marginal value beyond what's in the schema, meeting the baseline expectation when schema coverage is high.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Ask NVIDIA USDCode for help' with specific domains listed (Isaac Sim scripting, USD, Python/API tips). This provides a clear verb+resource combination. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or contextual constraints. The only usage-related information is a technical warning about avoiding changing temperature and top_p together, which doesn't address the broader 'when to use' question.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
B3.1/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined purpose of providing help with NVIDIA USDCode topics, so an agent cannot misselect between multiple options.
Naming Consistency5/5
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_usdcode_help' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
Tool Count2/5
A single tool is too few for a server with a broad purpose like 'NVIDIA USDCode MCP Server', which suggests coverage of Isaac Sim scripting, USD, and Python/API tips. This minimal toolset feels thin and under-scoped, limiting the server's utility for diverse agent tasks.
Completeness2/5
The tool surface is severely incomplete for the implied domain. While 'get_usdcode_help' might assist with queries, there are obvious gaps such as tools for executing code, managing USD files, or interacting with Isaac Sim APIs. This will likely cause agent failures when trying to perform specific actions beyond general help.
Maintenance
ActivityInactive
ResponsivenessNo issues
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Search NVIDIA CUDA documentation and code samples from AI coding agents.
Search and query nTop's knowledge base and engineering guides from AI applications.
Connect Claude, Cursor, Codex, and other AI tools to your robotics mission data.
Build, validate, and deploy multi-agent AI solutions from any AI environment.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables natural language control of NVIDIA Isaac Sim through the Model Context Protocol, allowing you to create robots, build scenes, run simulations, and debug physics from any MCP-compatible IDE.4260MIT
- FlicenseAqualityDmaintenanceEnables AI coding assistants to browse Unreal Python API documentation, search classes and functions, and execute Python code in Unreal Editor.8
- AlicenseNot gradedqualityDmaintenanceEnables AI tools like Windsurf and Claude to control NVIDIA Isaac Sim and Isaac Lab through natural language, providing tools for scene inspection, prim management, physics simulation, and robot spawning.8Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ishandotsh/nvidia-usdcode-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server