NotebookLM MCP
Related Servers
Alternatives to NotebookLM MCP
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.4912,935 PyPI6,145MIT
- 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
- AlicenseAqualityBmaintenanceConnects AI coding agents to Google NotebookLM, enabling querying notebooks, adding sources, and generating artifacts like reports, podcasts, and slide decks.141MIT
- 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
- 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 gradedqualityDmaintenanceEnables interaction with Google NotebookLM to create notebooks, add sources (PDF, URL, YouTube), and ask questions with citations.1MIT
TDQS
Scored across 27 tools
Each tool targets a distinct resource and action: notebook management, source operations, research tasks, artifact creation, query, and auth. Despite many artifact creation tools, each clearly specifies its output type (audio, video, infographic, etc.), so no two tools appear to do the same thing.
Most tools follow a resource_action pattern (e.g., notebook_create, source_delete, report_create), which is consistent. A few outliers like save_auth_tokens and refresh_auth use action_resource order, and research_status and studio_status are noun_noun compounds, but these are minor deviations within a largely coherent scheme.
At 27 tools, the server exceeds the 25-tool threshold for 'too many'. The count is inflated by 8 separate artifact creation tools that could be unified into a single tool with a type parameter, and the three add-source tools similarly could be consolidated. While the server covers a broad domain, the tool surface is heavier than necessary.
The tool set covers the full lifecycle for notebooks (create, read, list, rename, delete), sources (add three types, delete, describe, get content, sync), research (start, status, import), and artifacts (create and check status). Minor gaps exist such as no explicit list_sources tool (though notebook_get provides sources) and no update_source, but these are manageable workarounds.