You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/README.md
+1-26Lines changed: 1 addition & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -476,32 +476,7 @@ uv run python examples/quickstart/10_skills.py
476
476
477
477
### MCP tools
478
478
479
-
MCP (Model Context Protocol) tools let your agent call external services through a standard interface. The TUI ships MCP as a hard dependency (`self.mcp` and `/mcp` are always available). In the core library, MCP is an optional extra (`uv add 'nooa[mcp]'`).
480
-
481
-
**TUI configuration** — declare MCP servers in `.nooa/settings.yaml`:
482
-
483
-
```yaml
484
-
tui:
485
-
mcp_auto_connect: ["maas-confluence-stg"]
486
-
mcp_servers:
487
-
maas-confluence-stg:
488
-
url: "https://your-mcp-server.example.com/mcp"
489
-
transport: "streamable-http"
490
-
headers:
491
-
Authorization: "Bearer ${MAAS_API_KEY}"
492
-
```
493
-
494
-
At startup the TUI attaches auto-connected servers to the agent, so `maas-confluence-stg` becomes `self.maas_confluence_stg`. A VS Code / Claude-style `.mcp.json` file is also supported via `mcp_file` or `--mcp-file`.
495
-
496
-
Inside the TUI, servers are managed through `self.mcp` (an `MCPRegistry` skill that mirrors `self.skills`):
497
-
498
-
- `self.mcp.discovered()`— configured server names
499
-
- `await self.mcp.connect(["name"])`— open a server and attach it as `self.<name>`
500
-
- `self.mcp.activate([...])`/ `self.mcp.deactivate([...])` — control whether a connected server's tools are listed for the agent
501
-
- `<mcp>`context block lists every server each turn under **Active**, **Connected but inactive**, or **Configured**
**Library use** — no `self.mcp`; call the stateless `MCPManager` factory directly:
479
+
MCP (Model Context Protocol) tools let your agent call external services through a standard interface. Install with `uv add 'nooa[mcp]'` and call the stateless `MCPManager` factory:
CLI and TUI for [nemo-oo-agents](https://github.com/NVIDIA-NeMo/labs-OO-Agents). Ships the `nooa` command (subcommands like `nooa tui`, `nooa term`, `nooa eval`, `nooa traces`) and the agent TUI (a REPL-driven CodeAct frontend).
3
+
CLI for [nemo-oo-agents](https://github.com/NVIDIA-NeMo/labs-OO-Agents). Ships the `nooa` command with subcommands for running evaluations, browsing traces, and managing config.
4
4
5
5
## Install
6
6
7
7
```bash
8
-
# CLI + TUI
9
8
uv add nooa-cli
10
9
11
10
# ...with numpy/pandas/plotly/scipy/sklearn pre-loaded into the LLM REPL
`nooa-cli` automatically pulls in matching `nemo-oo-agents` (the core framework). The `[datascience]` extra adds libraries the LLM can use in REPL-generated code; the `[web]` extra adds the `nooa term` web frontend.
14
+
`nooa-cli` automatically pulls in matching `nemo-oo-agents` (the core framework). The `[datascience]` extra adds libraries the LLM can use in REPL-generated code.
19
15
20
16
## Usage
21
17
22
18
```bash
23
19
nooa --help
24
-
nooa tui # interactive agent REPL
25
-
nooa term # web terminal
20
+
nooa start-dev # launch the trace viewer
26
21
nooa eval ... # eval pipeline runner
22
+
nooa traces ... # inspect/manage trace files
27
23
```
28
24
29
25
See the main repo [README](https://github.com/NVIDIA-NeMo/labs-OO-Agents/blob/main/README.md) for the framework documentation.
0 commit comments