NotebookLM MCP Server
Related Servers
Alternatives to NotebookLM MCP Server
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.5312,514 PyPI6,246MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive Google NotebookLM notebooks as a deep-research workspace: ingesting local PDFs and YouTube videos, cross-checking sources for contradictions, identifying knowledge gaps, generating audio overviews, and exporting Markdown dossiers with BibTeX and APA bibliographies. It operates over the Model Context Protocol inside Google Antigravity IDE, with browser-session authentication handled automatically.MIT
- 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
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Google NotebookLM, allowing notebook management, source ingestion, deep research, and content generation directly from the terminal or IDE.27143 npm20MIT
TDQS
Scored across 38 tools
Most tools target clearly distinct resources (notebook_*, source_*, studio_*, chat_*, research_*, share_*). A few boundaries blur: source_add overlaps with source_add_drive_file and source_add_play_book, and chat_ask vs chat_start differ only by blocking vs detached execution. Descriptions do explicitly disambiguate these overlaps, so misselection is largely avoidable.
The set follows a strong resource_verb convention (notebook_rename, source_add, studio_generate, chat_ask, research_start, share_set_user). A few tools break the pattern (note_save, suggest_prompts, server_info, await_upload), but these are minor deviations that stay readable.
38 tools is heavy and pushes past the comfortable range. The domain (notebooks, sources, studio artifacts, chat, research, sharing) is genuinely broad so many tools earn their place, but the several source_add* variants and chat ask/start/status family suggest consolidation was possible.
Coverage spans the full lifecycle: notebooks (create/list/rename/delete/describe), sources (add/list/read/delete/rename/wait), studio artifacts (generate/status/download/rename/retry/delete/list), chat (ask/start/status/cancel/configure), research, sharing, and server health. No obvious dead ends in the domain.