notebooklm

# NotebookLM ## Overview NotebookLM answers questions **only from the sources uploaded to a notebook**, with inline citations to the exact passages used — no open-web knowledge, so answers are hallucination-resistant and fully traceable. This skill drives the `@roomi-fields/notebooklm-mcp` engine to query notebooks, manage sources, and generate Studio content, and encodes the patterns that make NotebookLM usable at research scale (citation formats, the ~50-queries/day quota, batch-to-cache). ## Choosing the transport Two ways reach the same engine — pick per what the session already has: 1. **notebooklm MCP tools** — if tools such as `notebook_ask` / `source_add` / `server_health` (or `mcp__notebooklm__*`) are available in the session, call them directly. This is the preferred path and needs no server. 2. **HTTP REST API** — otherwise, use the bundled `scripts/nblm.sh`, which talks to a running NotebookLM MCP server (default `http://localhost:3000`, override with `NOTEBOOKLM_SERVER_URL`). If no server is reachable, ask the user to start one (`npm run start:http` from a clone) or to install the MCP. Both are backed by the same account and session, so the choice is purely about which is already wired up. ## Prerequisite: one Google login NotebookLM needs a signed-in Google session (saved once, reused across runs). Verify with `nblm.sh health` (or the `server_health` tool) — look for `authenticated: true`. If not authenticated, run the interactive login **...