NVIDIA AI CKG MCP
An MCP server providing access to NVIDIA AI Knowledge Graphs across 21 domains, offering structured retrieval with SHA-256 provenance and reduced token usage compared to standard RAG. It supports integration with Claude Desktop, Cursor, Windsurf, and Python LangChain environments.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://ckg-nvidia-ai.onrender.com/mcpWhat its tools do
9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Integrate knowledge graph retrieval into Claude Desktop via MCP configuration
- Connect Cursor or Windsurf to NVIDIA AI knowledge domains
- Use Python LangChain CKGRetriever for domain-specific queries
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- ckg-nvidia-ai 1.30.0
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 9 advertised
- Resources
- 1 advertised
- Resource templates
- 1 advertised
- Prompts
- 3 advertised
{
"tools": {
"listChanged": false
},
"prompts": {
"listChanged": false
},
"resources": {
"subscribe": false,
"listChanged": false
},
"experimental": {}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
9 advertised
list_domains
List all 21 NVIDIA AI domains available in this knowledge graph.
{
"type": "object",
"title": "list_domainsArguments",
"properties": {}
}{
"type": "object",
"title": "list_domainsOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}search_concepts
Find concepts in a NVIDIA AI domain by keyword. Args: query: Search term — e.g. 'inference', 'sandbox', 'quantization', 'guardrails'. domain: Domain name from list_domains() — e.g. 'nvidia-nim', 'nvidia-openshell'.
{
"type": "object",
"title": "search_conceptsArguments",
"required": [
"query",
"domain"
],
"properties": {
"query": {
"type": "string",
"title": "Query"
},
"domain": {
"type": "string",
"title": "Domain"
}
}
}{
"type": "object",
"title": "search_conceptsOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}query_ckg
Traverse the NVIDIA knowledge graph from a concept — prerequisites and dependents. Args: concept: Concept name (partial match supported) — e.g. 'TensorRT', 'NIM', 'Isaac Lab'. domain: Domain name from list_domains() — e.g. 'nvidia-tensorrt-triton', 'nvidia-isaac'. depth: Traversal depth 1–5 (default 3).
{
"type": "object",
"title": "query_ckgArguments",
"required": [
"concept",
"domain"
],
"properties": {
"depth": {
"type": "integer",
"title": "Depth",
"default": 3
},
"domain": {
"type": "string",
"title": "Domain"
},
"concept": {
"type": "string",
"title": "Concept"
}
}
}get_prerequisites
Return the full ordered prerequisite chain for a concept — everything to learn first. Args: concept: Target concept — e.g. 'Speculative Decoding', 'Isaac Lab', 'NeMo Guardrails'. domain: Domain name from list_domains().
{
"type": "object",
"title": "get_prerequisitesArguments",
"required": [
"concept",
"domain"
],
"properties": {
"domain": {
"type": "string",
"title": "Domain"
},
"concept": {
"type": "string",
"title": "Concept"
}
}
}ask_nvidia
Ask a natural-language question answered by Qwen grounded on the NVIDIA CKG. Requires Ollama running locally with a Qwen model pulled: ollama pull qwen2.5:14b Override model: NVIDIA_CKG_MODEL env var (default: qwen2.5:14b) Override host: NVIDIA_CKG_OLLAMA env var (default: http://localhost:11434) Args: question: Natural-language question about the NVIDIA AI stack. domain: Domain from list_domains() — auto-detected from question if omitted.
{
"type": "object",
"title": "ask_nvidiaArguments",
"required": [
"question"
],
"properties": {
"domain": {
"type": "string",
"title": "Domain",
"default": ""
},
"question": {
"type": "string",
"title": "Question"
}
}
}{
"type": "object",
"title": "ask_nvidiaOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}list_ecosystem
Discover other CKG packages for adjacent domains — finance, healthcare, legal, and more.
{
"type": "object",
"title": "list_ecosystemArguments",
"properties": {}
}{
"type": "object",
"title": "list_ecosystemOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}route_query
Route an NVIDIA AI question to the optimal model and reasoning approach via graph depth. The CKG graph IS the router — hop depth is a deterministic complexity metric. Deeper NVIDIA prerequisite chains (CUDA → TensorRT → TensorRT-LLM → NIM) require more capable models. No heuristic: the graph decides. Routing table: hop_depth 1 → haiku · direct (simple lookup) hop_depth 2 → sonnet · generic_cot (moderate chain) hop_depth 3+ → opus · sparql_cot (deep dependency, structured reasoning) Args: question: Concept name or natural language question about NVIDIA AI. domain: Domain from list_domains() — e.g. "nvidia-tensorrt-triton", "nvidia-nim". Returns: model_tier + reasoning_approach + why + context subgraph to inject before LLM call.
{
"type": "object",
"title": "route_queryArguments",
"required": [
"question"
],
"properties": {
"domain": {
"type": "string",
"title": "Domain",
"default": ""
},
"question": {
"type": "string",
"title": "Question"
}
}
}{
"type": "object",
"title": "route_queryOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}verify_source
Return the source URL and SHA-256 content hash for any NVIDIA AI concept node. Audit chain: edge answer → graph commit → source_content_hash → source_url (fetch hint). Verification: curl -s <source_url> | sha256sum # compare to source_hash Args: concept: Concept label (partial match supported). domain: Domain from list_domains() — e.g. 'nvidia-nim', 'nvidia-tensorrt-triton'.
{
"type": "object",
"title": "verify_sourceArguments",
"required": [
"concept",
"domain"
],
"properties": {
"domain": {
"type": "string",
"title": "Domain"
},
"concept": {
"type": "string",
"title": "Concept"
}
}
}{
"type": "object",
"title": "verify_sourceOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}query_intersect
Answer a conjunctive query: concepts reachable from EVERY anchor at once (A AND B). query_ckg walks outward from one concept. This intersects the reachable sets of two or more, which is the shape of most real questions — "the component that satisfies A AND applies to B". Neither anchor alone answers it; the answer lives in the overlap. Every branch is an exact set of declared edges, so the intersection is exact. A concept appears only if a declared path reaches it from each anchor. A relation missing from the graph produces an empty result, never a guess. Args: branches: Two or more branches. Either a bare anchor ("TensorRT-LLM"), which takes everything within `depth` hops, or an anchor plus an explicit relation path using '>' ("TensorRT-LLM > REQUIRES > ENABLES"), where each relation replaces the frontier. '*' matches any relation. Mix both forms freely. domain: Domain name from list_domains(). depth: Hops for bare-anchor branches, 1-5 (default 2). Ignored for explicit paths. direction: 'out' follows dependencies, 'in' follows them backwards, 'both' (default). mode: 'AND' (default) intersects branches; 'OR' unions them. limit: Max concepts listed, 1-200 (default 40). The true count is always shown. Returns: Markdown with the query plan and its per-step set sizes, then the answer set with taxonomy tags. Reports which branch was empty when the intersection is empty.
{
"type": "object",
"title": "query_intersectArguments",
"required": [
"branches",
"domain"
],
"properties": {
"mode": {
"type": "string",
"title": "Mode",
"default": "AND"
},
"depth": {
"type": "integer",
"title": "Depth",
"default": 2
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 40
},
"domain": {
"type": "string",
"title": "Domain"
},
"branches": {
"type": "array",
"items": {
"type": "string"
},
"title": "Branches"
},
"direction": {
"type": "string",
"title": "Direction",
"default": "both"
}
}
}Prompts
3 advertised
explore_nvidia_stack
Build an interactive graph of the NVIDIA AI inference and robotics stack
map_deployment_chain
Map the full dependency chain for a production NVIDIA AI deployment
find_what_i_need
Tell me what I need to get started with a specific NVIDIA technology
Resources
1 advertised
resource_domains
All 21 NVIDIA AI domains — browsable index
ckg://domainsresource_domain
Full CKG for a single NVIDIA AI domain — nodes, edges, metadata
ckg://nvidia/{domain}90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-06: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 895 ms
- 95th percentile latency
- 895 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 895 ms · metadata changed · 9 tool(s), 1 resource(s), 1 resource template(s), 3 prompt(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http nvidia-ai-ckg-mcp https://ckg-nvidia-ai.onrender.com/mcpCodex
codex mcp add nvidia-ai-ckg-mcp --url https://ckg-nvidia-ai.onrender.com/mcpCursor
{
"mcpServers": {
"nvidia-ai-ckg-mcp": {
"url": "https://ckg-nvidia-ai.onrender.com/mcp"
}
}
}Cline
{
"mcpServers": {
"nvidia-ai-ckg-mcp": {
"type": "streamableHttp",
"url": "https://ckg-nvidia-ai.onrender.com/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"nvidia-ai-ckg-mcp": {
"type": "http",
"url": "https://ckg-nvidia-ai.onrender.com/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http nvidia-ai-ckg-mcp https://ckg-nvidia-ai.onrender.com/mcpClaude Desktop
https://ckg-nvidia-ai.onrender.com/mcpWindsurf
{
"mcpServers": {
"nvidia-ai-ckg-mcp": {
"serverUrl": "https://ckg-nvidia-ai.onrender.com/mcp"
}
}
}Let your agent find its tools
Find servers like NVIDIA AI CKG MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.