Skip to main content
Glama
jacob-bd

notebooklm-mcp

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to notebooklm-mcp

No user-submitted related servers found.

    Related Servers

    • notebooklm-mcp-cli

      hungln105-cell
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to programmatically access and manage Gemini Notebook (formerly Google NotebookLM), including creating notebooks, adding sources, querying content, generating studio content, downloading artifacts, and running batch or cross-notebook workflows through natural language.
      49
      MIT

    • NotebookLM MCP Server

      ignitabull18
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables interaction with Google's NotebookLM through natural language, allowing users to create and manage notebooks, add sources from URLs/YouTube/Google Drive, query AI for insights, generate audio podcasts and other studio content, and perform AI-powered research and analysis.
      32
      3
      MIT

    • nblm-mcp

      Diego-Dev-Moros
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with Google NotebookLM, including listing and managing notebooks and sources, asking grounded questions with citations, and generating audio overviews, briefings, quizzes, and mind maps.
      13
      MIT

    • NotebookLM MCP Server

      ran-ai-agency
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Google NotebookLM through natural language to create and manage notebooks, add sources from URLs/YouTube/Google Drive, perform AI-powered research and analysis, generate audio podcasts, videos, infographics, and slide decks from notebook content.
      32
      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.1/5.0

    Scored across 50 tools

    Disambiguation3/5

    Most tools separate cleanly by resource (notebook_, source_, collection_, studio_, research_), but several overlap: cross_notebook_query vs. batch's query action, report vs. studio_create, and download_artifact/export_artifact/download_all_artifacts could be confused. Descriptions mostly clarify intent, so an agent can usually pick correctly, but the boundaries are not always crisp.

    Naming Consistency2/5

    The resource-prefix pattern (notebook_get, collection_list, source_add) is visible but broken by bare-noun umbrella tools like tag, label, note, batch, pipeline, and report. Mixing noun_verb names with action-first names like download_artifact and research_start makes the naming convention unpredictable.

    Tool Count2/5

    50 tools is far beyond the well-scoped range, even though several tools consolidate many sub-operations. The broad NotebookLM domain justifies some sprawl, but the overall surface is heavy and burdensome for an agent to navigate.

    Completeness4/5

    The tool set covers notebook/source/collection CRUD, sharing, research workflows, chat, studio artifact creation/download/export/delete, auth, usage, labels, notes, tags, and batch operations. Minor gaps such as collaborator removal or a general artifact listing don't create fatal dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources