notebooklm-mcp
Related Servers
Alternatives to notebooklm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to programmatically access and control Google NotebookLM, supporting operations like notebook management, source addition, audio generation, and more via natural language.39MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to programmatically access and manage Gemini Notebook (formerly Google NotebookLM), including creating notebooks, adding sources, querying content, generating studio content, downloading artifacts, and running batch or cross-notebook workflows through natural language.49MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Google NotebookLM notebooks, add sources from URLs, YouTube, Drive, or text, query and summarize content, and generate audio overviews, infographics, and slide decks through natural language.MIT
- AlicenseAqualityNot gradedmaintenanceEnables interaction with Google's NotebookLM through natural language, allowing users to create and manage notebooks, add sources from URLs/YouTube/Google Drive, query AI for insights, generate audio podcasts and other studio content, and perform AI-powered research and analysis.323MIT
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Google NotebookLM, including listing and managing notebooks and sources, asking grounded questions with citations, and generating audio overviews, briefings, quizzes, and mind maps.13MIT
- AlicenseAqualityDmaintenanceEnables interaction with Google NotebookLM through natural language to create and manage notebooks, add sources from URLs/YouTube/Google Drive, perform AI-powered research and analysis, generate audio podcasts, videos, infographics, and slide decks from notebook content.32MIT
TDQS
Scored across 53 tools
Most tools target distinct resources (notebooks, sources, chat, studio, collections, tags, labels, research, sharing), and the async query workflow is well documented. A few overlaps remain: chat_get vs chat_export, and download_artifact / download_all_artifacts / export_artifact could be confused, plus three parallel organizational systems (collections, tags, labels).
The dominant pattern is domain_prefix_action in snake_case (notebook_create, source_rename, studio_status), which is highly consistent. The main deviation is a set of bare-noun 'unified' tools (label, alias, pipeline, note, tag, report, batch), which read differently but are at least a deliberate, documented grouping.
53 tools is very heavy even for a feature-rich NotebookLM wrapper covering notebooks, sources, chat, studio artifacts, research, sharing, auth and pipelines. Several clusters (download/export, research, query variants, studio lifecycle) could be consolidated or namespaced into fewer entry points.
Coverage is broad and lifecycle-complete: full CRUD for notebooks, sources, collections, notes, tags and labels, plus studio artifact create/status/revise/download/delete, chat management, research workflow, sharing, and auth handling. No obvious dead-end operations.