Skip to main content
Glama
leanhduy-iuh

NotebookLM MCP Server

by leanhduy-iuh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to NotebookLM MCP Server

No user-submitted related servers found.

    Related Servers

    • notebooklm-mcp

      jacob-bd
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to programmatically interact with Google NotebookLM, allowing them to create and manage notebooks, add sources, query content, generate audio/video, and perform research tasks through natural language commands.
      49
      12,935 PyPI
      6,096
      MIT

    • 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

    • 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

      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
    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

    A3.6/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (notebook_*, source_*, studio_*, research_*), and the async query start/status split is clearly documented. Minor overlap exists between notebook_share_invite vs notebook_share_batch and between download_artifact vs export_artifact, but descriptions disambiguate them adequately.

    Naming Consistency4/5

    A predictable resource_action snake_case pattern dominates (notebook_list, source_add, studio_create, research_start). The only deviations are the unified single-word action tools (note, tag, label, batch, pipeline) and prefix-less helpers (refresh_auth, server_info), which are still readable and consistent within themselves.

    Tool Count3/5

    39 tools is heavy and near the upper bound, even for a feature-rich domain. Several consolidated multi-action tools (note, tag, label, batch, studio_create, source_add) reduce sprawl, but the surface still feels broad and could likely be trimmed further.

    Completeness5/5

    The surface covers the full lifecycle: notebook CRUD+describe, source add/get/sync/rename/delete/describe, note CRUD, studio create/status/revise/delete/download/export, sharing, research, tags, labels, and auth management. No obvious operational gaps remain for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources