Bragproof

← Reports

notebooklm-mcp

Starts with no setup2.0.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing

20tools listed
0hosts contacted
1file written
0.4 sto start
123dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y notebooklm-mcp@2.0.0

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 5 returned a result.

list_notebooksReturned a result under 0.1 s · 58 characters
get_library_statsReturned a result under 0.1 s · 197 characters
list_sessionsReturned a result under 0.1 s · 193 characters
get_healthReturned a result under 0.1 s · 568 characters
get_audio_statusReturned a result under 0.1 s · 81 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

ask_question question, session_id, notebook_id, notebook_url, source_format, show_browser, browser_options
# Conversational Research Partner (NotebookLM • Gemini 2.5 • Session RAG)

## No Active Notebook
- Visit https://notebooklm.google to create a notebook and get a share link
- Use **add_notebook** to add it to your library (explains how to get the link)
- Use **list_notebooks** to show available sources
- Use **select_notebook** to set one active

> Auth tip: If login is required, use the prompt 'notebooklm.auth-setup' and then verify with the 'get_health' tool. If authentication later fails (e.g., expired cookies), use the prompt 'notebooklm.auth-repair'.

Tip: Tell the user you can manage NotebookLM library and ask which notebook to use for the current task.
add_notebook url, name, description, topics, content_types, use_cases, tags
Register a NotebookLM notebook in the local library so it can be queried with `ask_question`, ingested into with `add_source`, etc.

## Required URL
The user must supply a NotebookLM share-link. To produce one:
  1. Open https://notebooklm.google
  2. Open the notebook → click "Share" (top right)
  3. Set "Anyone with the link" → "Copy link"

## Permission workflow
Do NOT call this tool unprompted. The expected dialogue is:
  1. Ask for the URL
  2. Ask what knowledge it contains (1–2 sentences) → `description`
  3. Ask which topics it covers (3–5) → `topics`
  4. Ask when it should be consulted → `use_cases`
  5. Propose a `name` and the metadata back to the user
  6. Only after explicit confirmation, call `add_notebook`.

Free-tier limits: 100 notebooks · 50 sources each · 50 queries/day. Google AI Pro/Ultra raises these 5×.
list_notebooks
List every notebook in the local library with its metadata (`id`, `name`, `description`, `topics`, `tags`, `url`, `use_count`, etc.). Use the returned `id` for `select_notebook`, `update_notebook`, `get_notebook`, `remove_notebook`, or as `notebook_id` on `ask_question` / `add_source` / audio tools.
get_notebook id
Fetch full metadata for one notebook by id. Use to verify what's currently stored before calling `update_notebook`, or to show the user the exact `description`/`topics`/`use_cases` Claude has for it.
select_notebook id
Mark a notebook as the active default. After this, `ask_question`, `add_source`, and the audio tools resolve to that notebook when the caller omits `notebook_id` / `notebook_url`.

When to call:
  • The user explicitly switches context (e.g. "Let's work on React now")
  • Task obviously needs a different notebook than the current one — announce the switch ("Switching to the React notebook…") before calling.
  • If the right notebook is ambiguous, ask the user first instead of guessing.
15 more tools
update_notebook id, name, description, topics, content_types, use_cases, tags, url
Patch metadata fields on an existing notebook. Pass `id` plus any subset of `name`, `description`, `topics`, `content_types`, `use_cases`, `tags`, `url` — only supplied fields change.

Workflow: identify the target notebook → propose the exact change back to the user → call only after explicit confirmation. Multiple fields can be updated in one call.
remove_notebook id
Remove a notebook from the local library. **Does NOT delete the actual NotebookLM notebook on Google's side** — only the local metadata entry. Active sessions on this notebook are closed.

Confirmation workflow: look up the notebook by id, ask the user "Remove '[name]' from your library?" — only call after a clear yes.
search_notebooks query
Search the library by free-text query — matches against `name`, `description`, `topics`, and `tags`. Returns notebook objects with their `id` so you can chain into `select_notebook` etc.

Use this when the user references a notebook by topic ("the React one") instead of by exact name. If multiple notebooks match, propose the top 1–2 and let the user choose.
get_library_stats
Aggregate statistics about the local notebook library: `total_notebooks`, `active_notebook` (id), `most_used_notebook`, `total_queries`, `last_modified`. Useful as a quick health check or when the user asks "what notebooks do I have?".
list_sessions
List all active browser sessions for this server. Each entry includes `id`, `created_at`, `last_activity`, `age_seconds`, `inactive_seconds`, `message_count`, and `notebook_url`. Useful before `reset_session` / `close_session` or to recover a `session_id` you can pass back into `ask_question` to continue an existing conversation. Sessions older than `session_timeout` (see `get_health`) are auto-closed.
close_session session_id
Permanently close a session and discard its browser tab. Use the `id` returned by `list_sessions` (or the `session_id` from a prior `ask_question` response). Closed sessions cannot be resumed — start a new one with `ask_question` (no `session_id`) or pick another from `list_sessions`. Ask the user before closing if the session might still be needed.
reset_session session_id
Clear a session's chat history while keeping the same session id. Use this when the task changes mid-conversation and you want a fresh context without losing the underlying browser tab. Ask the user before resetting if they might still need the prior history.
get_health
Inspect server state. Returns:
  • `authenticated` — whether saved Google cookies are still valid
  • `notebook_url`, `active_notebook_id`, `active_notebook_name` —
    the currently selected library notebook (or null)
  • `total_notebooks` — library size
  • `active_sessions`, `max_sessions`, `session_timeout` — runtime
    session stats (timeout in seconds; sessions auto-close after this)
  • `headless`, `auto_login_enabled`, `stealth_enabled` — config
Use this first thing in a new conversation. If `authenticated=false`, run `setup_auth` (or `re_auth` to switch accounts).
setup_auth show_browser, browser_options
Open a browser window for first-time Google login. Returns immediately after spawning the browser; the user has up to 10 minutes to complete sign-in, then cookies are persisted for future runs.

When to use:
  • `get_health` reports `authenticated=false` for the first time
  • Auto-login credentials are not configured
  • `re_auth` is the right call when you want to *switch* accounts or recover from a daily-quota lockout

After login finishes, call `get_health` to verify success.

If the browser session feels broken (auth keeps failing, stale cookies), run `cleanup_data(confirm=true, preserve_library=true)` first, then retry `setup_auth`.
re_auth show_browser, browser_options
Switch to a different Google account or recover from broken auth. Closes all active sessions, deletes saved cookies and Chrome profile, and opens a fresh login browser.

Common triggers:
  • NotebookLM's 50 queries/day free-tier limit is reached and the user wants to rotate to another Google account
  • `setup_auth` failed and a clean slate is needed

After login, call `get_health` to verify. For very stuck states, run `cleanup_data(confirm=true, preserve_library=true)` before `re_auth`.
cleanup_data confirm, preserve_library
Two-phase deep cleanup of all server data on disk (auth state, browser profiles, caches, MCP logs, temp backups). Cross-platform (Linux/macOS/Windows). Always close all Chrome/Chromium instances first — open browsers can lock files.

Phase 1 (preview): call with `confirm: false`. Returns a categorised list of paths and total size. **No deletion happens.**
Phase 2 (delete): after the user reviews the preview and approves, call with `confirm: true`.

Set `preserve_library: true` to keep the notebook library file (library.json) while wiping everything else — recommended when troubleshooting auth.

Typical recovery flow:
  1. cleanup_data(confirm=false, preserve_library=true)  // preview
  2. cleanup_data(confirm=true, preserve_library=true)   // execute
  3. setup_auth (or re_auth)
add_source type, content, title, show_browser, session_id, notebook_id, notebook_url
Ingest a source into a NotebookLM notebook. Supports two source types in v2.0:
  • `url` — NotebookLM crawls and indexes a website
  • `text` — paste raw text (treated as a copied document)

File / YouTube / Google-Drive uploads are not yet implemented.

Returns `sourceCountBefore`/`sourceCountAfter` so the caller can verify the new source landed. Call once per source — multiple sources require multiple calls. NotebookLM finishes indexing within 5–30 seconds; subsequent `ask_question` calls then have the new source in context. Free notebooks cap at 50 sources.

Known quirk: pasted-text uploads occasionally redirect to a freshly created "Untitled notebook" on Google's side. The tool detects this and returns a clear error so you can re-try against the correct URL.
generate_audio custom_prompt, wait_for_completion, timeout_ms, show_browser, session_id, notebook_id, notebook_url
Trigger podcast-style Audio Overview generation for a notebook.

**Async by default** — returns immediately with one of:
  • `status: "started"` — generation just kicked off
  • `status: "in_progress"` — a generation was already running; this call attached to it
  • `status: "ready"` (with `alreadyExisted: true`) — an Audio Overview already existed; nothing was triggered

Generation typically takes 2–10 minutes. **Workflow:**
  1. `generate_audio` → returns immediately
  2. Poll `get_audio_status` every ~30 s
  3. When status is `ready`, call `download_audio`

Pass `wait_for_completion: true` for legacy synchronous behaviour (blocks for up to `timeout_ms`). Audio Overview is the only Studio output exposed in v2.0 (Video / Mindmap / Quiz / Infographic / Datatable / Presentation are NotebookLM features but not yet wrapped).
get_audio_status show_browser, session_id, notebook_id, notebook_url
Non-blocking probe for the current Audio Overview state of a notebook.

Returned `status` values:
  • `ready` — Audio Overview is generated and ready to download
  • `in_progress` — generation is currently running
  • `not_started` — no Audio Overview exists yet for this notebook

Safe to poll every ~30 s while waiting for `generate_audio` to finish. When status flips to `ready`, call `download_audio` with a destination directory.
download_audio destination_dir, show_browser, session_id, notebook_id, notebook_url
Save the completed Audio Overview to disk as a `.m4a` file. **Pre-condition:** `get_audio_status` must report `status: "ready"`. Calling this before generation completes returns an error message explaining what to do.

The file lands in `destination_dir` with NotebookLM's suggested filename (sanitised — usually the audio's title with underscores). The full saved path is returned in `result.filePath`.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnode >=18.0.0
Sourcegithub.com/PleasePrompto/notebooklm-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-7OGz3A1MKLmQHcHx448hYzYaOwjpGehM0VC0VH+5QmHuUQDSNtGOXWnJB+0Cr3x1M5uRip3A+qy4q6cIRY0qWA==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/notebooklm-mcp.svg)](https://bragproof.smaverk.com/r/notebooklm-mcp)

New version out? Ask for a fresh report.