📓 notebooklm-mcp

MCP (Model Context Protocol) server for Google NotebookLM — source-grounded, citation-backed answers from your own documents, inside Claude Code and any MCP client.

🇬🇧 English · 🇧🇷 Português

⚠️ Notice. Unofficial project, not affiliated with Google. Automating a logged-in session may be considered automated access under NotebookLM's Terms, with risk to your account. Use at your own risk. Subject to usage limits (e.g. ~50 questions/day on the free plan).

✨ Highlights

• Source-grounded answers — every reply comes from your uploaded documents (Gemini), drastically reducing hallucinations.

• Any MCP client — works with Claude Code, Cursor, and anything that speaks the Model Context Protocol over stdio.

• No official API — browser automation with Patchright, reusing a logged-in Google session.

• Smart Add — NotebookLM itself describes a notebook's name, content, and topics so your library stays accurate.

• Zero Python friction — pure TypeScript/Node, distributed via npx. No interpreter, venv, or pip.

Related MCP server: notebooklm-mcp

📋 Prerequisites

🚀 Installation & usage

# 1. Interactive login (once; opens the browser for you to log in to Google)
npx @rinaldops/notebooklm-mcp login

# 2. Register with Claude Code (consumed over stdio)
claude mcp add notebooklm -- npx -y @rinaldops/notebooklm-mcp

# Library management (optional; equivalent MCP tools also exist)
npx @rinaldops/notebooklm-mcp notebooks add "<url>" "My Notebook" "Description" "topic1,topic2"
npx @rinaldops/notebooklm-mcp notebooks list           # local library
npx @rinaldops/notebooklm-mcp notebooks remote         # all notebooks in the account
npx @rinaldops/notebooklm-mcp notebooks describe <url> # Smart Add: discovers the notebook's metadata

💡 Prefer the editor experience? Install the VS Code extension in packages/extension — it registers the server and auto-configures Claude Code / Cursor in your workspace.

Smart Add (catalog with automatic metadata)

Recommended flow to populate the library without making up descriptions:

1. notebooks remote (or the notebooklm_list_remote_notebooks tool) → get the URL.

2. notebooks describe <url> (or notebooklm_describe_notebook) → NotebookLM itself describes the name, content, and topics.

3. notebooks add <url> <name> <description> <topics> based on step 2.

🧰 Exposed tools

⚙️ Configuration (env)

🛠️ Development

Monorepo with npm workspaces:

• packages/mcp-server — the MCP server (publishable via npx).

• packages/extension — the VS Code extension (registers/auto-configures the server). Built with tsup; debug with F5 (Extension Development Host).

npm install                 # install all workspaces (from the root)
npm run build               # build all packages
npm run typecheck

# Server commands (run inside the package):
cd packages/mcp-server
npm run dev -- login        # login via tsx, no build
npm start                   # node dist/cli.js (after build)

See PLAN.md for the development plan and the status of each part, and CHANGELOG.md for release history.

📄 License

MIT © 2026 Rinaldo Paulino de Souza. Unofficial project, not affiliated with Google — use at your own risk; see the notice at the top.