NVIDIA CUDA Docsvf.sr

listing.by · home.legend.verified

Search current first-party NVIDIA CUDA documentation and code samples from your AI coding agent.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs

listing.note.oauth

listing.share.h

listing.share.p

mcp.tc/i/nvidia-cuda-docs

listing.about

Connects an AI coding agent to NVIDIA's first-party CUDA documentation and code examples, so answers about CUDA development come from current sources instead of model memory. It is part of NVIDIA's Nsight AI offering.

The server is hosted by NVIDIA and uses the streamable HTTP transport. On first connection you sign in with an NVIDIA Developer account through OAuth, and the client reuses that sign-in afterward. Nothing needs to be installed locally.

listing.can

  • Search NVIDIA CUDA documentation
  • Find CUDA code samples and examples
  • Ground CUDA answers in current first-party sources
  • Use from agents such as Claude Code, Codex and Cursor

listing.tools

listing.notools.oauth

listing.prompts

  • How do I avoid uncoalesced global memory accesses in my CUDA kernel?

  • Find an NVIDIA code sample for using shared memory in a matrix multiply.

  • What does the CUDA docs say about cudaMallocAsync?

  • Show the recommended way to launch a cooperative groups kernel.

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http nvidia-cuda-docs https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs
  1. Start Claude Code, type /mcp, pick nvidia-cuda-docs and choose Authenticate. A browser window opens for the NVIDIA sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it NVIDIA CUDA Docs and paste this URL:
https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs
  1. Click Add, then Connect, and sign in when NVIDIA asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs and click Add.
  2. Click Connect and sign in when NVIDIA asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs as the server URL and choose OAuth. ChatGPT sends you to NVIDIA to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "nvidia-cuda-docs": {
      "url": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"nvidia-cuda-docs","type":"http","url":"https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "nvidia-cuda-docs": {
      "type": "http",
      "url": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "nvidia-cuda-docs": {
      "serverUrl": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add nvidia-cuda-docs --url https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs
codex mcp login nvidia-cuda-docs

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.nvidia-cuda-docs]
url = "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"

Gemini CLI

gemini mcp add --transport http nvidia-cuda-docs https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs

Then, inside Gemini CLI, run /mcp auth nvidia-cuda-docs to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "nvidia-cuda-docs": {
      "type": "http",
      "url": "https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs.

listing.faq

Can I paste mcp.tc/i/nvidia-cuda-docs into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs, so your client talks to NVIDIA CUDA Docs directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does NVIDIA CUDA Docs need an API key or a sign-in?

Yes, you need a NVIDIA account. The first time your client connects, it opens NVIDIA's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is NVIDIA CUDA Docs a remote or a local server?

Remote. NVIDIA hosts it at https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs, and it speaks Streamable HTTP. There's nothing to install.

What can NVIDIA CUDA Docs do?

You can search NVIDIA CUDA documentation, find CUDA code samples and examples and ground CUDA answers in current first-party sources.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read NVIDIA CUDA Docs's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![NVIDIA CUDA Docs on mcp.tc](https://mcp.tc/i/nvidia-cuda-docs/badge.svg)](https://mcp.tc/i/nvidia-cuda-docs)
HTML
<a href="https://mcp.tc/i/nvidia-cuda-docs"><img src="https://mcp.tc/i/nvidia-cuda-docs/badge.svg" alt="NVIDIA CUDA Docs on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/nvidia-cuda-docs.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/nvidia-cuda-docs" title="NVIDIA CUDA Docs on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/nvidia-cuda-docs.json

listing.em.fields

listing.disclaimer_checked