A
licenseNot graded
qualityC
maintenanceMCP server for querying Google NotebookLM notebooks, enabling AI assistants to list notebooks, read sources, and ask questions about them.
MIT
notebooklm-mcp
by brock-run
Related Servers
Alternatives to notebooklm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to Google NotebookLM, enabling natural language interaction with notebooks, including Q&A, source ingestion, and audio overview generation.1,742 npmMIT
- FlicenseBqualityDmaintenanceA production-ready, fully asynchronous MCP server that bridges AI agents with Google NotebookLM, enabling notebook creation, source management, audio generation, and more through natural language.12-
- AlicenseNot gradedqualityBmaintenanceCustom MCP server for NotebookLM that adds audio source upload, YouTube source ingestion, source readiness polling, and transcript export, complementing standard Q&A and audio overview tools.MIT
- AlicenseNot gradedqualityAmaintenanceSecure MCP server for querying Google NotebookLM notebooks. Enables AI assistants to list notebooks, read sources, and ask the NotebookLM AI questions about your sources.92 PyPI16MIT
- AlicenseBqualityAmaintenanceMCP server that provides ~39 tools to interact with Google NotebookLM's internal API, enabling notebook management, source addition, chat queries, and Studio artifact generation through stdio, HTTP, and SSE transports.39MIT
TDQS
A3.5/5.0
Scored across 14 tools
Disambiguation5/5
Each tool targets a distinct resource-action combination: metadata operations are clearly separated into validate/get/set/query, notebook operations into list/get/create/delete/share, and sources/audio each have their own dedicated tools. Even get_notebook and get_source are unambiguous because one returns notebook details with sources and the other returns a specific source's details.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern with the notebooklm_ prefix. Action verbs such as get, set, list, create, delete, add, remove, generate, and share are used predictably across the tool set.
Tool Count5/5
14 tools is well within the ideal range for a domain-specific MCP server. The count covers notebooks, sources, metadata, sharing, and audio without feeling bloated or thin.
Completeness4/5
The tool surface provides strong lifecycle coverage for notebooks, sources, metadata, and audio overviews. Minor gaps exist such as no explicit notebook update/rename operation, no standalone list-sources tool, and no unshare or list-audio tools, but these are workable gaps rather than critical dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues