Skip to main content
Glama
inventra

NotebookLM MCP Server

by inventra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to NotebookLM MCP Server

No user-submitted related servers found.

    Related Servers

    • NotebookLM MCP Server

      tpelletier70
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code, Cursor, and Codex to interact with Google NotebookLM for citation-backed Q&A, source management, and generation of audio, video, infographics, reports, presentations, data tables, study aids, and mind maps, with multi-account rotation and auto-reauth. Also provides the same capabilities over a local HTTP REST API for n8n, Zapier, Make, and curl.
      2,962 npm
      MIT

    • NotebookLM MCP Server

      nikoslemoine
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents like Claude Code, Cursor, and Codex to drive Google NotebookLM for citation-backed question answering and full Studio generation of audio, video, infographics, reports, presentations, data tables, flashcards, quizzes, and mind maps. Supports multi-account rotation with automatic re-authentication for high-volume batch runs across notebooks.
      2,962 npm
      MIT

    • NotebookLM MCP Server

      Sebastiend7049
      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.
      2,962 npm
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is some overlap between close_session and reset_session (both manage sessions), and between setup_auth and re_auth (both handle authentication). The descriptions help clarify differences, but an agent might occasionally misselect between these pairs.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., add_notebook, list_notebooks, get_health), with minor deviations like cleanup_data (noun_verb) and ask_question (verb_noun but less structured). Overall, the naming is readable and mostly predictable.

    Tool Count4/5

    16 tools are reasonable for managing NotebookLM notebooks, sessions, authentication, and cleanup. It covers core workflows without being overly heavy, though some tools like cleanup_data are specialized and might be used infrequently.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for NotebookLM notebooks (add, list, get, update, remove, search, select) and sessions (list, close, reset), plus authentication, health checks, and cleanup. No obvious gaps exist for the server's purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources