A short, hand-picked list — not a marketplace. Every entry is reviewed against one question: would this genuinely help someone who uses NotebookLM?
3 picks so far · reviewed by the Sourclip team
NotebookLM MCP Server(MIT) — Drives a real Chrome session against NotebookLM so an agent can chat with a notebook, add sources, generate audio overviews, and read DOM-level citations. Great for: Runs a stealth, persistent Chrome profile behind the scenes — you log into Google once, then every later run is headless. Every answer comes back with a provenance envelope that marks it as AI-generated and flags any instructions embedded in third-party PDFs as untrusted input, which matters if you're piping notebook answers into other tool calls. Tool profiles (minimal/standard/full) let you trim what's exposed to keep an agent's context budget in check.
NotebookLM REST API + MCP Server(MIT) — Generates every NotebookLM Studio output — audio, video, infographics, reports, presentations, data tables — plus a 33-endpoint REST API for n8n, Zapier, or Make. Great for: The widest feature surface of the NotebookLM automation servers: full Studio content generation, multi-account rotation with automatic TOTP re-authentication for overnight batch runs, and a Docker + noVNC path for headless/NAS deployment. An optional RTFM integration writes citation-backed answers to a searchable offline vault, which suits academic workflows that need to ask the same notebook hundreds of questions. The changelog shows a real pattern of fast, iterative bug-fixing between releases — worth knowing if you want a slower-moving dependency.
NotebookLM MCP (khengyun)(MIT) — A no-browser take on NotebookLM automation — talks to an RPC backend instead of driving Chrome, and can merge sources across notebooks or generate mind maps. Great for: Built on notebooklm-py, an RPC client, so there's no Chrome process to keep alive at runtime — a lighter-weight option if you don't need DOM-level citation scraping. Its 28 tools cover the usual chat/manage/source set plus two things the other options don't: merging sources from multiple notebooks into a new one, and generating/reading mind maps. Smallest and least-adopted of the three NotebookLM automation servers, but actively maintained.
Before you install an MCP server
Does NotebookLM support MCP? Not yet — NotebookLM doesn't expose an MCP client, so these servers don't plug directly into it. What they do is extend the MCP clients you already use for research (Claude Code, Cursor, and others) with search, documents, and notebook control.
A note on safety: MCP servers can access local files, credentials, or paid APIs once connected. Install only from publishers you trust, and review what permissions you're granting before you connect one.