Skip to main content
Glama
Sign In
notebooklm-mcp

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
      D
      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/5.0

    Scored across 55 tools

    Disambiguation2/5

    Several tools have overlapping or hard-to-distinguish retrieval/organization purposes: notebook_query, source_search, cross_notebook_query, batch query, and research_start all relate to finding or asking about content. Vague unified tools like alias, tag, note, pipeline, label, report, batch, and profile require action parameters and add ambiguity, while profile/active_profile/profiles are especially easy to confuse.

    Naming Consistency3/5

    Most resource-specific tools use a readable noun_verb pattern (notebook_create, source_add, studio_status), but many unified tools are bare nouns or vague action containers (alias, tag, note, pipeline, label, report, batch, profile). The mix of noun_verb, verb_noun, and single-word names is understandable but not predictable.

    Tool Count1/5

    With 55 tools, the surface is far too large for a coherent MCP server. Many variants and unified action tools could be consolidated into fewer, better-scoped tools.

    Completeness4/5

    Coverage is broad: notebooks, sources, chat, studio artifacts, research, collections, tags, labels, sharing, auth, batch operations, and usage are all represented. Minor lifecycle gaps remain, such as limited collection retrieval or source content update, but the core NotebookLM workflows are well covered.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources