What it does
This MCP server automates Google NotebookLM by driving a real Chrome browser via Patchright. It lets agents chat with notebooks, ingest sources, generate audio overviews, and extract DOM-level citations. Supports both stdio and HTTP transports for flexible integration with Claude Code, Cursor, generic MCP clients, and hosted agents. Uses persistent Chrome profiles for authentication — you log in once and subsequent runs reuse the stored cookies. Multi-account support allows running distinct Chrome profiles for different Google accounts.
Who it's for
Developers building AI agents or Claude-powered workflows that need programmatic access to NotebookLM. Teams automating research workflows, notebook generation, or citation extraction within their AI pipelines. Anyone integrating NotebookLM into a larger automation system rather than using the web interface.
Common use cases
- Chat with a NotebookLM notebook from Claude Code to ask questions or iterate on research
- Ingest sources (documents, links, PDFs) into a notebook programmatically
- Generate audio overviews of notebook content via the API
- Extract structured citations and source references from notebook analysis
- Automate workflows across multiple Google accounts using distinct Chrome profiles
Setup pitfalls
- Initial authentication requires a display; on headless Linux servers, run once under
xvfb-runthen subsequent runs go fully headless - Requires
Node.js≥ 18 and either Chrome (stable channel) or Patchright Chromium - WSL1 cannot launch Chromium; WSL2 with WSLg is required on Windows 11+
- Reads and writes filesystem; ensure the sandbox has appropriate permissions to access Chrome profile storage