Generated banner for Nemo Retriever MCP
Generated logo for Nemo Retriever MCP

Nemo Retriever MCP

NVIDIAOfficialPublished by NVIDIA

  • Skill
  • Tool integration
  • Automation and integrations
  • Apache-2.0
  • Medium risk

From the author

Use when a task needs to search or add documents through NeMo Retriever MCP.
— the description by NVIDIA

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The NeMo Retriever MCP skill provides a structured interface for interacting with the NeMo Retriever service via the Model Context Protocol (MCP). It enables agents to perform semantic searches across indexed documents and ingest new content when necessary. The skill emphasizes using specific tool calls for querying and ingestion while ensuring that agents properly ground their responses in the retrieved evidence, including maintaining document identifiers for accurate citations.

What it does

  • Provides access to NeMo Retriever MCP tools for document retrieval and ingestion.
  • Supports querying existing document indices to find relevant information.
  • Facilitates the ingestion of new documents into the retriever system.
  • Guides the agent to ground answers using retrieved evidence hits.
  • Ensures document metadata and identifiers are preserved for citation purposes.

When to use it

  • When an agent needs to search through a collection of documents to answer a user query.
  • When new documents must be added to the retriever index for future searchability.
  • When the task requires evidence-based responses with specific source citations.
  • When working within an environment that supports NeMo Retriever MCP server tools.

Advantages

  • Standardizes the interaction pattern for document retrieval tasks.
  • Promotes accurate grounding by requiring evidence hits to be read and cited.
  • Prevents redundant ingestion of already searchable documents.
  • Provides clear error handling and retry guidance for query operations.

Usage examples

“Search for information regarding the company's Q3 policy in the retriever.”
The agent uses the query tool with a search string, retrieves the top 5 hits, and synthesizes an answer citing the specific document IDs and page numbers provided.
“Ingest the document at /shared/data/policy.pdf and then find the section on remote work.”
The agent calls ingest_documents for the specified path, confirms success, and then performs a query to extract the requested information about remote work.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/nemo-retriever-mcp/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip nemo-retriever-mcp.zip -d .agents/skills

Documentation by NVIDIA

NeMo Retriever MCP

Use the NeMo Retriever MCP tools exposed under retriever instead of the retriever CLI.

The server exposes MCP tools, not MCP resources. Do not call list_mcp_resources to discover documents or decide whether Retriever is available; an empty MCP resource list is expected.

Workflow

  • Use query to search documents already available to Retriever.

  • Never ingest documents that are already searchable, including documents in a prebuilt index.

  • Use ingest_documents only when required documents are not yet searchable and server-readable paths are explicitly available. Do not assume that paths visible to the agent are also readable by the Retriever server.

  • After ingestion completes, use query to retrieve evidence from the added documents.

  • Start with top_k=5 and format="hits". Request more only when the first successful response does not contain enough evidence to answer the task.

  • Read evidence hits from the tool response and ground your answer in them.

  • Preserve available document identifiers such as document_id, source_id, or pdf_basename, along with page numbers, when the task requests citations or structured output.

  • If query fails, inspect the error and retry with corrected parameters or a shorter equivalent query. If it still fails, report the error before using another retrieval method.

Files

evals/evals.json

[
  {
    "id": "nemo-retriever-mcp-001",
    "question": "Use NeMo Retriever MCP to find passages that mention \"climate change\" in the already indexed research_reports collection.",
    "expected_skill": "nemo-retriever-mcp",
    "expected_script": "None",
    "ground_truth": "The agent queried the existing collection without ingesting it and returned the matching passages with available document identifiers and page numbers as citations.",
    "expected_behavior": [
      "The agent read the nemo-retriever-mcp SKILL.md before using Retriever MCP tools",
      "The agent called the Retriever MCP query tool with top_k=5 and format=\"hits\" initially, requesting more results only if needed",
      "The agent did not call ingest_documents because the collection was already indexed",
      "The agent did not call list_mcp_resources to discover documents or test Retriever availability",
      "The agent returned matching excerpts with available document identifiers and page-number citations",
      "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
    ]
  },
  {
    "id": "nemo-retriever-mcp-002",
    "question": "Search the documents already available in NeMo Retriever and summarize the sections that discuss risk management, with citations.",
    "expected_skill": "nemo-retriever-mcp",
    "expected_script": "None",
    "ground_truth": "The agent queried the documents already available to Retriever, summarized the retrieved risk-management evidence, and cited the available source identifiers and page numbers.",
    "expected_behavior": [
      "The agent read the nemo-retriever-mcp SKILL.md before using Retriever MCP tools",
      "The agent called the Retriever MCP query tool with top_k=5 and format=\"hits\" initially",
      "The agent did not call ingest_documents because the documents were already available to Retriever",
      "The agent grounded the summary in retrieved evidence and preserved available document identifiers and page numbers",
      "The agent did not call list_mcp_resources to discover documents or test Retriever availability",
      "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
    ]
  },
  {
    "id": "nemo-retriever-mcp-003",
    "question": "The NeMo Retriever server can read /data/contracts, and those documents are not indexed yet. Add the collection, then retrieve clauses about data privacy and provide citations.",
    "expected_skill": "nemo-retriever-mcp",
    "expected_script": "None",
    "ground_truth": "The agent ingested the explicitly server-readable contracts directory, queried it for data-privacy clauses, and returned the retrieved clauses with available document identifiers and page numbers.",
    "expected_behavior": [
      "The agent read the nemo-retriever-mcp SKILL.md before using Retriever MCP tools",
      "The agent called the Retriever MCP ingest_documents tool for /data/contracts because the path was explicitly server-readable and the documents were not indexed",
      "After ingestion completed, the agent called the Retriever MCP query tool for data-privacy clauses",
      "The agent started the query with top_k=5 and format=\"hits\", requesting more results only if needed",
      "The agent returned the retrieved clauses with available document identifiers and page-number citations",
      "The agent did not call list_mcp_resources to discover documents or test Retriever availability",
      "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
    ]
  },
  {
    "id": "nemo-retriever-mcp-004",
    "question": "How do I bake a chocolate cake from scratch?",
    "expected_skill": null,
    "expected_script": "None",
    "ground_truth": "The agent provided a step-by-step chocolate cake recipe without loading the nemo-retriever-mcp skill or calling Retriever MCP tools.",
    "expected_behavior": [
      "The agent responded with a chocolate cake recipe without invoking Retriever MCP tools",
      "The agent did not read the nemo-retriever-mcp SKILL.md",
      "The agent did not call query, ingest_documents, or list_mcp_resources",
      "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
    ]
  }
]

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
NVIDIA
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/nemo-retriever-mcp · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download nemo-retriever-mcp.zip