NVIDIA CUDA Docs MCP Server

by nvidia-ngc-nsight-copilot-api Your server? Claim it

answering

NVIDIA CUDA Docs is answering right now. Last checked 10 min ago.

Search NVIDIA CUDA documentation and code samples from AI coding agents.

Uptime history 91 days of history · worst day 96%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

810 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

NVIDIA CUDA Docs missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://api.copilot.nsight.ngc.nvidia.com/mcp/cuda-docs	streamable-http	sign-in	815 ms	10 min ago

Alternatives to NVIDIA CUDA Docs

same job, measured the same way

Semlith

by semlith

Local search over your code and documents for AI agents.

local only

SMSPVA Documentation

by smspva

SMSPVA API docs: search and code examples for SMS activation, number rental and private email.

4 tools answering

Codealive MCP

by codealive-ai

Semantic code search and analysis from CodeAlive for AI assistants and agents.

local only

XERJ

by xerj-org

The search engine for AI agents: cited answers from your local code, docs, specs and logs.

local only

Miru

by takara

Hybrid semantic and keyword code search for coding agents.

304 installs/wk local only

Vocenya Docs

by vocenya

Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.

4 tools answering

Docfork MCP

by smithery

@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singl…

answering

CodeNib

by codenib

Source-linked CodeGraph exploration, ranked search, and static navigation for coding agents.

876 installs/wk local only

NVIDIA CUDA Docs — questions

Answers built from our own checks of this server.

Why is there no tool list for NVIDIA CUDA Docs?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is NVIDIA CUDA Docs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 810 ms. The bar chart above shows every period we have measured.

How do I connect NVIDIA CUDA Docs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to NVIDIA CUDA Docs?

No API key is involved. NVIDIA CUDA Docs answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is NVIDIA CUDA Docs?

It answers our handshake in 810 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.