Skip to main content
Glama
cast-ai-tech

notebooklm-mcp

by cast-ai-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to notebooklm-mcp

No user-submitted related servers found.

    Related Servers

    • notebooklm-mcp-2026

      Faxtom
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying Google NotebookLM notebooks, enabling AI assistants to list notebooks, read sources, and ask questions about them.
      MIT

    • notebooklm-mcp-2026

      julianoczkowski
      A
      license
      Not graded
      quality
      A
      maintenance
      Secure MCP server for querying Google NotebookLM notebooks. Enables AI assistants to list notebooks, read sources, and ask the NotebookLM AI questions about your sources.
      92 PyPI
      16
      MIT

    • Notebooklm-Unofficial-API-MCP

      DevstackK
      A
      license
      Not graded
      quality
      C
      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.
      MIT

    • notebooklm-mcp

      KeiosStarqua
      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.
      1,742 npm
      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.4/5.0

    Scored across 39 tools

    Disambiguation5/5

    Each tool has a well-defined and distinct purpose, with descriptions that clearly differentiate similar tools (e.g., notebook_query vs research_start vs cross_notebook_query). The batch and category tools (label, note, tag) namespace their sub-actions, preventing confusion.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., notebook_create, source_add, studio_create), but a few tools are nouns representing a category of operations (label, note, tag, pipeline, batch). While the sub-actions within these are verbs, the top-level names deviate slightly.

    Tool Count3/5

    39 tools is on the high side, but the server covers a broad and complex domain (NotebookLM). Each tool serves a specific purpose, though some could potentially be consolidated further (e.g., share tools). The count is borderline heavy but not unreasonable.

    Completeness5/5

    The tool surface covers all major lifecycle phases: CRUD for notebooks, sources, notes, and artifacts; research pipeline; sharing; tags/labels; batch operations; and auth management. There are no obvious gaps for the intended domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources