notebooklm-mcp

What it does

NotebookLM MCP Server automates interactions with Google NotebookLM through browser automation. It drives a real Chrome browser via Patchright (with stealth and fingerprint persistence) to enable Claude to chat with notebooks, ingest new sources, generate audio overviews, and read DOM-level citations. The server maintains persistent Chrome profiles so subsequent runs reuse stored authentication, supports both stdio and HTTP transports, and works across Linux, macOS, Windows, and WSL2.

Who it's for

Researchers, analysts, and knowledge workers who want to integrate NotebookLM programmatically into Claude workflows—automating source ingestion, synthesis, and citation extraction without manual browser interaction.

Common use cases

• Query an existing NotebookLM notebook to extract citations or synthesize content in context
• Batch-ingest new sources into notebooks and generate study material summaries
• Generate audio overviews and retrieve the resulting transcripts programmatically
• Automate multi-source research where Claude adds sources, synthesizes findings, and retrieves formatted citations
• Run separate NotebookLM accounts per team member or workflow using multi-account support

Setup pitfalls

• Requires Node.js ≥18 and Chrome (stable) or fallback Chromium; on headless Linux, initial setup_auth must run under xvfb-run to display the Google login window
• WSL1 is not supported—upgrade to WSL2+
• Persistent Chrome profile lives in the user's home directory and is account-specific
• The browser window process may be visible on first-time setup; subsequent runs reuse cached authentication