notebooklm-mcp-server
Related Servers
Alternatives to notebooklm-mcp-server
No user-submitted related servers found.
Related Servers
- 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-
- 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
- AlicenseAqualityCmaintenanceEnables AI assistants to programmatically access and control Google NotebookLM, supporting operations like notebook management, source addition, audio generation, and more via natural language.39MIT
- AlicenseAqualityBmaintenanceConnects AI coding agents to Google NotebookLM, enabling querying notebooks, adding sources, and generating artifacts like reports, podcasts, and slide decks.141MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google NotebookLM to create notebooks, add sources (PDF, URL, YouTube), and ask questions with citations.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Google NotebookLM through browser automation, supporting notebook management, source addition, question answering, and audio overview generation.2MIT
TDQS
Scored across 29 tools
Each tool targets a distinct operation or resource. Overlaps exist (e.g., multiple 'create' tools) but are disambiguated by their specific output types (audio, video, flashcards, etc.) and clear descriptions.
Most tools follow a <resource>_<action> pattern (e.g., notebook_create, mind_map_delete). The outlier 'refresh_auth' uses verb_noun instead, which is a minor inconsistency.
29 tools cover a wide range of NotebookLM features (notebooks, sources, multiple outputs, research, mind maps, studio). While slightly high, each tool serves a distinct purpose within the scope.
The tool surface covers the full lifecycle: CRUD for notebooks and sources, generation of various outputs, research workflow, and studio management. No obvious gaps for the intended use cases.