Skip to main content
Glama
roomi-fields

notebooklm-mcp

by roomi-fields
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to notebooklm-mcp

No user-submitted related servers found.

    Related Servers

    • Notebooklm-Unofficial-API-MCP

      DevstackK
      A
      license
      Not graded
      quality
      C
      maintenance
      A thin MCP wrapper around the unofficial Google NotebookLM Python client, enabling notebook management, source handling, chat, artifact generation, deep research, and sharing via MCP tools.
      MIT

    • notebooklm-mcp

      KeiosStarqua
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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 npm
      MIT

    • gemini-notebook-mcp

      abderrahim-lectures
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for Google NotebookLM that lets AI agents chat with notebooks, add sources, generate audio overviews, and extract citations via a real Chrome browser.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 39 tools

    Disambiguation2/5

    Multiple tools have overlapping or confusing boundaries: library_list vs notebook_list both list notebooks (local metadata vs actual account), content_list vs source_list both list sources, content_generate vs generate_study_aid/generate_mind_map all generate artifacts, and library_remove vs notebook_delete distinguish only by subtle naming. The descriptions are thorough, but the tool names alone leave several pairs easily confused.

    Naming Consistency2/5

    The majority follow prefix patterns (library_, source_, note_, content_, auth_, session_, notebook_), but six outliers break it: vault_batch, share_notebook, generate_study_aid, generate_mind_map, manage_labels, research_sources. Worse, descriptions consistently reference tool names that don't exist (e.g., 'call add_notebook' for library_add, 'setup_auth' for auth_setup, 'list_content' for source_list), making the naming scheme unreliable.

    Tool Count2/5

    39 tools is well above the 25+ threshold for a heavy surface. The scope is broad (library, auth, sessions, sources, content, notes, notebooks, sharing, labels), but there is clear redundancy—two list-notebook tools, two list-sources tools, and three generate tools—that could have been consolidated.

    Completeness3/5

    Core workflows are covered: notebook ask/create/delete, source add/list/read/delete, content generate/list/download, notes create/list/get, and auth/session management. Notable gaps remain—no rename/update for actual notebooks, no delete/edit for notes, no delete for generated content, and the descriptions explicitly admit several content types (faq, study_guide, timeline, table_of_contents) are unimplemented.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources