Gemini Notebook by Chryzalide (agy-gemini-notebook-plugin)
Related Servers
Alternatives to Gemini Notebook by Chryzalide (agy-gemini-notebook-plugin)
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityDmaintenanceBridges Claude Code/Cowork with Google NotebookLM for AI-powered research, source analysis, chat, and content generation through a structured tool interface.MIT
- AlicenseNot gradedqualityBmaintenanceExposes Google NotebookLM as MCP tools, enabling management of notebooks, sources, chat, artifacts, and research via natural language.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables citation-backed Q&A and full Studio content generation (audio, video, infographics, reports, presentations, data tables, flashcards, quizzes, mind maps) against Google NotebookLM, with multi-account rotation and auto-reauth. Serves both MCP clients like Claude Code and Cursor and a 33-endpoint HTTP REST API for no-code tools such as n8n, Zapier, and Make.2,214 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants and agents to connect directly to Google NotebookLM through its high-performance internal RPC calls. Provides grounded RAG chat with citations, notebook and source management (URLs, YouTube, Drive files, text), Audio Overview generation and download, persistent session handling, and automated Deep Research.381MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Google NotebookLM notebooks directly from Claude Desktop (MCP) and Claude Code (CLI), providing citation-backed answers from Gemini.MIT
TDQS
Scored across 21 tools
Several tools overlap in practice: `notebook_get` and `notebook_invoke` without a question both return metadata/summary, and `notebook_query` versus `notebook_invoke` with a question are functionally near-identical grounded Q&A paths. `notebook_add_source` and `notebook_sync_files` also both ingest content, and `notebook_notes` bundles five actions into one tool. Descriptions do disambiguate somewhat, but boundary choice requires careful reading.
All 21 tools use a consistent snake_case `notebook_*` prefix, which makes the family instantly recognizable. Minor deviation: some names are verb-first (create, delete, rename, list, query) while others are noun/state-like (`notebook_status`, `notebook_notes`, `notebook_research_status`), but the pattern remains readable and predictable.
21 tools is on the heavy side for a single-product integration, and the dual-engine (GCP REST vs RPC bridge) design is baked into tool parameters rather than split into separate surfaces. Most tools map to a real operation, but the set sits at the upper edge of what an agent can hold comfortably in one context.
Coverage is broad: notebook lifecycle, sources, notes, grounded search/query, research sessions, sharing, file sync, and artifact generation. Gaps exist around updating notebook metadata (only `notebook_rename`), editing/replacing sources, and retrieving or listing generated artifacts after creation. These are workarounds-able but notable.