NotebookLM REST API + MCP Server
Generates every NotebookLM Studio output — audio, video, infographics, reports, presentations, data tables — plus a 33-endpoint REST API for n8n, Zapier, or Make.
License: MIT · Best for: Developers · Teams automating Studio content generation at scale
What it is
An MCP server and companion 33-endpoint REST API that generates every NotebookLM Studio output — Audio Overview, video, infographic, report, presentation, and data table — plus citation-backed Q&A, with multi-account rotation and automatic re-authentication built for overnight batch runs.
Why NotebookLM users should care
If you want more than a chat interface — you want NotebookLM's full Studio suite generated on a schedule, or you're wiring NotebookLM into n8n or Zapier rather than an MCP client — this is the widest feature surface of the three. The REST API means non-MCP tools can call it directly, and the multi-account rotation with TOTP re-authentication is built for exactly the kind of overnight, thousand-question batch run that would otherwise get logged out halfway through.
Key capabilities
- Full Studio generation: Audio Overviews, video (6 visual styles), infographics, reports, presentations, and data tables — all from one server.
- 33-endpoint REST API: Every MCP tool also exists as an HTTP endpoint, so n8n, Zapier, Make, or plain curl can drive NotebookLM without an MCP client.
- Multi-account rotation: Automatic TOTP re-authentication keeps long batch jobs running across multiple Google accounts without manual re-logins.
- Docker + noVNC deployment: Runs headless on a NAS or server, with a browser-based VNC window for the one-time visual login.
- RTFM vault integration: An optional batch-to-vault endpoint writes citation-backed answers to a searchable offline markdown vault for repeated querying.
Installation summary
Ships as both an MCP server and a standalone HTTP server; requires Node.js. The fastest path for Claude Code users is the plugin marketplace one-liner below. For HTTP/REST use, clone the repo, install and build it, then run the one-time auth setup and start the HTTP server. Full REST API reference and the Docker/NAS deployment guide are in the official docs.
/plugin marketplace add roomi-fields/claude-plugins && /plugin install notebooklm@roomi-fields
Official links
FAQ
Is this the same as the other NotebookLM MCP server in this list?
No — different project, same goal. This one adds a full REST API and complete Studio content generation (video, infographics, presentations, data tables); the tradeoff is a smaller GitHub following so far.
Do I need to use the REST API, or can I stick to MCP?
Both work standalone. Use MCP mode inside Claude Code, Cursor, or Codex; use HTTP mode if you're calling it from n8n, Zapier, Make, or a script.
Is it free?
Yes, MIT licensed and free to self-host.
What's the RTFM integration for?
It's an optional companion project that caches NotebookLM's citation-backed answers as a searchable local vault — useful if you're asking the same notebook hundreds of questions and want offline retrieval instead of re-querying NotebookLM every time.