A
licenseNot graded
qualityC
maintenanceExposes Google NotebookLM as MCP tools, enabling management of notebooks, sources, chat, artifacts, and research via natural language.
2
MIT
Notebooklm-Unofficial-API-MCP
by DevstackK
Related Servers
Alternatives to Notebooklm-Unofficial-API-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Google NotebookLM through MCP, supporting chat, source ingestion, audio overview generation, library management, and citation reading.4,977 npmMIT
- AlicenseAqualityBmaintenanceProvides CLI and MCP server to programmatically access Google NotebookLM, enabling AI assistants to create notebooks, add sources, generate podcasts, and more, with support for both personal and enterprise accounts.4114 PyPIMIT
- AlicenseBqualityCmaintenanceMCP 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
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Google NotebookLM through a unified CLI and MCP server, featuring automatic multi-browser authentication and support for notebook queries, source management, notes, and audio generation.MIT
- 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.4,977 npmMIT
TDQS
A3.6/5.0
Scored across 39 tools
Disambiguation3/5
Several tools overlap in purpose: source_add, source_add_drive_file, and source_add_play_book all add sources, while source_wait and await_upload both wait for source readiness, and chat_ask/chat_start/chat_status form a related set. The detailed descriptions clarify routing, but an agent can still face misselection across these families.
Naming Consistency4/5
Most names follow a clear domain_action convention (notebook_*, source_*, chat_*, share_*, studio_*, research_*). A few outliers like ping, await_upload, server_info, and suggest_prompts break the pattern, but the set is largely predictable.
Tool Count2/5
At 39 tools, the surface is well above the typical 15-tool sweet spot and includes several specialized variants that could be consolidated. While NotebookLM is a broad domain, the count feels over-granular rather than tightly scoped.
Completeness4/5
The set covers notebook, source, chat, sharing, studio, research, and note lifecycles, including add/read/rename/delete and async polling. Minor gaps remain, such as direct notebook metadata updates or source reprocessing/resync, but most core workflows are supported.