notebooklm-mcp-rpc
Related Servers
Alternatives to notebooklm-mcp-rpc
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceProduction-grade Model Context Protocol server for Google NotebookLM that lets any MCP-capable client (Claude, ChatGPT, Cursor, etc.) interact with NotebookLM notebooks, sources, chats, and artifacts.MIT
- AlicenseAqualityCmaintenanceAn unofficial MCP server for Google NotebookLM that enables users to manage notebooks, add sources, ask questions with citations, and generate audio podcasts via a Playwright-based automation layer.19MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Google NotebookLM notebooks, enabling AI assistants to list notebooks, read sources, and ask questions about them.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets CLI agents (Claude, Codex, Cursor) chat directly with Google NotebookLM for zero-hallucination answers based on user's own notebooks.1,595 npmMIT
- AlicenseAqualityDmaintenanceA robust MCP server for NotebookLM that provides auto-healing authentication, zero-config setup, and tools to list, query, create notebooks, and manage sources.62MIT
TDQS
Scored across 52 tools
Each tool has a clearly distinct purpose, targeting a specific resource and action. Even within the many 'generate' tools, the output type (audio, video, quiz, etc.) uniquely identifies each. No two tools appear to do the same thing.
Tool names predominantly follow the 'resource_action' pattern (e.g., artifact_delete, notebook_list), but a few use 'action_resource' (e.g., download_artifact, generate_audio). The mixing is minor and names remain descriptive and predictable.
With 52 tools, the count far exceeds the 'too many' threshold of 25+. While NotebookLM is a complex product, such a large tool surface can overwhelm an agent and suggests opportunities for consolidation (e.g., parameterizing generation types).
The tool set covers the full lifecycle of notebooks, sources, artifacts, notes, chat, research, sharing, and content generation. Every major operation (CRUD, import, export, configuration) is addressed with no obvious gaps for the domain.