Developer · Local MCP server
Nvidia Nim MCP
MCP server for NVIDIA NIM - 50+ LLMs, multimodal, image gen, embeddings, reranking.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.david-eve-za/nvidia-nim-mcp- Version
- 2.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-26
- Updated
- 2026-06-26
- Publisher
- david-eve-za (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/david-eve-za) · how
- Repository
- github.com/david-eve-za/nvidia-nim-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | nvidia-nim-mcp | 2.1.2 | stdio |
How to connect Nvidia Nim MCP
Nvidia Nim MCP runs locally from a Node.js package published to the npm registry: nvidia-nim-mcp version 2.1.2. 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-nim-mcp@2.1.2. It reads these environment variables: NVIDIA_API_KEY (required, secret), NVIDIA_NIM_BASE_URL, NVIDIA_AI_FOUNDATION_URL, DEFAULT_MODEL, ENABLE_IMAGE_GENERATION, ENABLE_VISION and ENABLE_MULTIMODAL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"nvidia-nim-mcp": {
"command": "npx",
"args": [
"-y",
"nvidia-nim-mcp@2.1.2"
],
"env": {
"NVIDIA_API_KEY": "<secret>",
"NVIDIA_NIM_BASE_URL": "<value>",
"NVIDIA_AI_FOUNDATION_URL": "<value>",
"DEFAULT_MODEL": "<value>",
"ENABLE_IMAGE_GENERATION": "<value>",
"ENABLE_VISION": "<value>",
"ENABLE_MULTIMODAL": "<value>"
}
}
}
}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
More developer servers
| Server | Runs |
|---|---|
| nuthatchQuery an EVM contract's indexed history with SQL, via a local nuthatch nest and nuthatch dev. | Local · stdio |
| NvdNVD MCP - wraps the NIST National Vulnerability Database API. | Remote · HTTPLive check: ✓ handshake |
| Nvd Cve MCPSearch CVE vulnerability records from the NIST NVD database. No key required. | Local · stdio |
| NVIDIA CUDA DocsSearch NVIDIA CUDA documentation and code samples from AI coding agents. | Remote · HTTPLive check: sign-in required |
| NytNYT MCP - wraps The New York Times Developer APIs (developer.nytimes.com) | Remote · HTTPLive check: ✓ handshake |
| nyxoryAgent-to-agent cloud service: deploys and runs your apps and services - domains, logs, real status. | Remote & Local · HTTP, stdioLive check: sign-in required |
| O360 MCPRun Offensive360 SAST scans (60+ languages) on local code; findings with file/line and fixes. | Local · stdio |
| Oauth AuditorScans MCP server auth code for OAuth 2.1 anti-patterns: token passthrough, missing audience. | Local · stdio |