notebooklm-mcp-cli
Related Servers
Alternatives to notebooklm-mcp-cli
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI assistants to programmatically interact with Google NotebookLM, allowing them to create and manage notebooks, add sources, query content, generate audio/video, and perform research tasks through natural language commands.24915,448 PyPI6,096MIT
- 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
- 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
- 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
- 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
- FlicenseAqualityDmaintenanceEnables AI agents to query and interact with Google NotebookLM notebooks to retrieve citation-backed information. It provides tools for listing notebooks, accessing source data, and asking natural language questions.11-
TDQS
Scored across 49 tools
Most tools have clearly distinct purposes (e.g., chat_list vs chat_get vs chat_export). Some potential confusion exists between notebook_query and research_start, but descriptions provide clear guidance. Unified tools like note, label, and tag manage different entity types, reducing ambiguity.
The majority of tool names follow a consistent verb_noun snake_case pattern (e.g., collection_create, source_delete, studio_revise). However, unified tools like 'note', 'label', 'tag', 'pipeline', and 'batch' deviate from this pattern by using single nouns, creating minor inconsistency.
With 49 tools, the server exceeds the 25+ threshold for being 'too many'. While the domain is broad, the number feels excessive and overwhelming, and some tools could have been consolidated further (e.g., download_artifact and download_all_artifacts could overlap). The count is appropriate for full coverage but leans heavy.
The tool set comprehensively covers the NotebookLM domain: notebook CRUD, source management, research workflows, chat, collections, studio artifacts, sharing, tags/labels, auth, usage, and batch operations. There are no obvious dead ends—every major workflow has associated tools for each lifecycle step.