by NVIDIA
A flexible, lightweight library that connects and optimizes teams of AI agents, enabling seamless integration with various frameworks, tools, and data sources.
The toolkit provides a unifying interface for building, composing, and managing AI agents across different frameworks (LangChain, LlamaIndex, CrewAI, Semantic Kernel, etc.). It focuses on reusability, rapid development, profiling, observability, evaluation, and full Model Context Protocol (MCP) support.
uv (≥0.5.4), Python 3.11/3.12.git clone git@github.com:NVIDIA/NeMo-Agent-Toolkit.git nemo-agent-toolkit
cd nemo-agent-toolkit
git submodule update --init --recursive
git lfs install
git lfs fetch
git lfs pull
uv venv --seed .venv --python 3.11 # or 3.12
source .venv/bin/activate
uv sync
To install all optional groups and plugins:
uv sync --all-groups --all-extras
uv pip install -e '.[<plugin_name>]' # e.g., uv pip install -e '.[langchain]'
nat --version
workflow.yaml defining tools, LLM, and a react_agent.NVIDIA_API_KEY.nat run --config_file workflow.yaml --input "List five subspecies of Aardvarks"
Q: Do I need to switch my existing agent framework? A: No. The toolkit sits on top of or alongside existing frameworks without requiring migration.
Q: Which Python versions are supported? A: Python 3.11 and 3.12.
Q: How do I add a new plugin (e.g., for LangChain)?
A: Install it from the packages directory, e.g., uv pip install -e '.[langchain]'.
Q: Can I use the toolkit without any optional extras?
A: Yes. Installing with uv sync provides the core functionality; extras add profiling, UI, and MCP capabilities.
Q: How do I run the toolkit as an MCP server?
A: Follow the documentation under docs/source/workflows/mcp/mcp-server.md to expose your tools via MCP.
Q: Where can I find more examples?
A: The examples folder in the repository contains ready‑to‑run workflows and detailed READMEs.

NVIDIA NeMo Agent Toolkit is a flexible, lightweight, and unifying library that allows you to easily connect existing enterprise agents to data sources and tools across any framework.
[!NOTE] NeMo Agent Toolkit was previously known as the Agent Intelligence (AIQ) toolkit, and AgentIQ. The library was renamed to better reflect the purpose of the toolkit and to align with the NVIDIA NeMo family of products. The core technologies, performance, and roadmap remain unchanged and the API is fully compatible with previous releases. Please refer to the Migration Guide for more information.
Automatic Hyperparameter Tuning: Automatically tune the hyperparameters of your agents, tools, and workflows to maximize performance, minimize cost, and increase accuracy.
Google ADK Support: Users of Google's Agent Development Kit (ADK) framework are now supported in NeMo Agent Toolkit.
MCP Authorization: NeMo Agent Toolkit now supports MCP authorization. This allows you to use NeMo Agent Toolkit with MCP authorization when using the streamable HTTP protocol.
Function Groups: NeMo Agent Toolkit now supports Function Groups, allowing you to package multiple related functions together to share configuration, context, and resources.
Amazon Bedrock AgentCore and Strands Agents Support: NeMo Agent Toolkit now supports building agents using Strands Agents framework and deploying them securely on Amazon Bedrock AgentCore runtime.
🧩 Framework Agnostic: NeMo Agent Toolkit works side-by-side and around existing agentic frameworks, such as LangChain, LlamaIndex, CrewAI, Microsoft Semantic Kernel, and Google ADK, as well as custom enterprise agentic frameworks and simple Python agents. This allows you to use your current technology stack without replatforming. NeMo Agent Toolkit complements any existing agentic framework or memory tool you're using and isn't tied to any specific agentic framework, LLM provider, or data source.
🔁 Reusability: Every agent, tool, and agentic workflow in this library exists as a function call that works together in complex software applications. The composability between these agents, tools, and workflows allows you to build once and reuse in different scenarios.
⚡ Rapid Development: Start with a pre-built agent, tool, or workflow, and customize it to your needs. This allows you and your development teams to move quickly if you're already developing with agents.
📈 Profiling: Use the profiler to profile entire workflows down to the tool and agent level, track input/output tokens and timings, and identify bottlenecks. While we encourage you to wrap (decorate) every tool and agent to get the most out of the profiler, you have the freedom to integrate your tools, agents, and workflows to whatever level you want. You start small and go to where you believe you'll see the most value and expand from there.
🔎 Observability: Monitor and debug your workflows with dedicated integrations for popular observability platforms such as Phoenix, Weave, and Langfuse, plus compatibility with OpenTelemetry-based observability platforms. Track performance, trace execution flows, and gain insights into your agent behaviors.
🧪 Evaluation System: Validate and maintain accuracy of agentic workflows with built-in evaluation tools.
💬 User Interface: Use the NeMo Agent Toolkit UI chat interface to interact with your agents, visualize output, and debug workflows.
🔗 Full MCP Support: Compatible with Model Context Protocol (MCP). You can use NeMo Agent Toolkit as an MCP client to connect to and use tools served by remote MCP servers. You can also use NeMo Agent Toolkit as an MCP server to publish tools via MCP.
With NeMo Agent Toolkit, you can move quickly, experiment freely, and ensure reliability across all your agent-driven projects.
Before you begin using NeMo Agent Toolkit, ensure that you have Python 3.11, 3.12, or 3.13 installed on your system.
[!NOTE] For users who want to run the examples, it's required to clone the repository and install from source to get the necessary files required to run the examples. Please refer to the Examples documentation for more information.
To install the latest stable version of NeMo Agent Toolkit from PyPI, run the following command:
pip install nvidia-nat
NeMo Agent Toolkit has many optional dependencies which can be installed with the core package. Optional dependencies are grouped by framework and can be installed with the core package. For example, to install the LangChain/LangGraph plugin, run the following:
pip install "nvidia-nat[langchain]"
Or for all optional dependencies:
pip install "nvidia-nat[all]"
Detailed installation instructions, including the full list of optional dependencies, can be found in the Installation Guide.
Before getting started, it's possible to run this simple workflow and many other examples in Google Colab with no setup. Click here to open the introduction notebook in a new tab: .
Ensure you have set the NVIDIA_API_KEY environment variable to allow the example to use NVIDIA NIMs. An API key can be obtained by visiting build.nvidia.com and creating an account.
export NVIDIA_API_KEY=<your_api_key>
Create the NeMo Agent Toolkit workflow configuration file. This file will define the agents, tools, and workflows that will be used in the example. Save the following as workflow.yml:
functions:
# Add a tool to search wikipedia
wikipedia_search:
_type: wiki_search
max_results: 2
llms:
# Tell NeMo Agent Toolkit which LLM to use for the agent
nim_llm:
_type: nim
model_name: meta/llama-3.1-70b-instruct
temperature: 0.0
workflow:
# Use an agent that 'reasons' and 'acts'
_type: react_agent
# Give it access to our wikipedia search tool
tool_names: [wikipedia_search]
# Tell it which LLM to use
llm_name: nim_llm
# Make it verbose
verbose: true
# Retry up to 3 times
parse_agent_response_max_retries: 3
Run the Hello World example using the nat CLI and the workflow.yml file.
nat run --config_file workflow.yml --input "List five subspecies of Aardvarks"
This will run the workflow and output the results to the console.
Workflow Result:
['Here are five subspecies of Aardvarks:\n\n1. Orycteropus afer afer (Southern aardvark)\n2. O. a. adametzi Grote, 1921 (Western aardvark)\n3. O. a. aethiopicus Sundevall, 1843\n4. O. a. angolensis Zukowsky & Haltenorth, 1957\n5. O. a. erikssoni Lönnberg, 1906']
examples directory of the source repository.We would love to hear from you! Please file an issue on GitHub if you have any feedback or feature requests.
We would like to thank the following groups for their contribution to the toolkit:
In addition, we would like to thank the following open source projects that made NeMo Agent Toolkit possible:
Please log in to share your review and rating for this MCP.
Explore related MCPs that share similar capabilities and solve comparable challenges
by modelcontextprotocol
An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process.
by danny-avila
Provides a self‑hosted ChatGPT‑style interface supporting numerous AI models, agents, code interpreter, image generation, multimodal interactions, and secure multi‑user authentication.
by block
Automates engineering tasks on local machines, executing code, building projects, debugging, orchestrating workflows, and interacting with external APIs using any LLM.
by RooCodeInc
Provides an autonomous AI coding partner inside the editor that can understand natural language, manipulate files, run commands, browse the web, and be customized via modes and instructions.
by pydantic
A Python framework that enables seamless integration of Pydantic validation with large language models, providing type‑safe agent construction, dependency injection, and structured output handling.
by mcp-use
A Python SDK that simplifies interaction with MCP servers and enables developers to create custom agents with tool‑calling capabilities.
by lastmile-ai
Build effective agents using Model Context Protocol and simple, composable workflow patterns.
by Klavis-AI
Provides production‑ready MCP servers and a hosted service for integrating AI applications with over 50 third‑party services via standardized APIs, OAuth, and easy Docker or hosted deployment.
by nanbingxyz
A cross‑platform desktop AI assistant that connects to major LLM providers, supports a local knowledge base, and enables tool integration via MCP servers.