Skip to main content
Glama

Related Servers

Alternatives to notebooklm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      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.
      39
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to drive Google NotebookLM for citation-backed Q&A over your sources, plus generation of audio, video, infographics, reports, presentations, data tables, flashcards, quizzes and mind maps, using multi-account rotation with automatic re-authentication. It also exposes the same engine as a local HTTP REST API for no-code and custom integrations.
      5,121 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      5,121 npm
      MIT
    • 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.
      MIT

    TDQS

    B3.4/5.0

    Scored across 56 tools

    Disambiguation2/5

    Many clusters overlap heavily: library_list vs notebook_list; library_add vs notebook_create vs library_discover; source_list/content_list/note_list; source_delete/content_delete/notebook_delete; content_generate vs generate_study_aid vs generate_mind_map; notebook_ask vs search_passages vs vault_batch. Descriptions also reference tool names that do not exist in this set (get_health, ask_question, add_notebook, list_sources, cleanup_data, setup_auth), which will actively mislead an agent choosing tools.

    Naming Consistency3/5

    All names are snake_case, but the ordering convention is mixed: noun_verb (source_delete, content_generate, notebook_copy) alongside verb_noun (delete_chat_history, get_source_guide, generate_mind_map). Some names are vague or omit the domain noun entirely (vault_batch, manage_labels, share_notebook), though most remain readable.

    Tool Count1/5

    56 tools is an extreme overshoot for a single NotebookLM integration and spans library management, browser auth, cleanup, sessions, sources, Studio artifacts, notes, research, and usage. Many operations could be consolidated or moved behind a smaller set of parameterized tools.

    Completeness4/5

    The surface is unusually comprehensive: notebook lifecycle, source ingestion/reading/deletion/copying, Studio generation/export/download, notes, chat, research, labels, sharing, auth, cleanup, and usage are all represented. Minor gaps remain, such as no direct NotebookLM-side notebook rename and several Studio content types explicitly marked as not implemented.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled