Skip to main content
Glama
paolodalprato

NotebookLM MCP Structured

Related Servers

Alternatives to NotebookLM MCP Structured

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      A BM25-based MCP server that enables document search and retrieval across structured domains of knowledge content, allowing Claude to search and reference documentation when answering questions.
      4
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that automatically enhances user prompts by applying advanced engineering techniques like chain-of-thought and few-shot reasoning based on identified intent. It optimizes technique selection through local learning and integrates directly into Claude sessions to improve output quality without additional API costs.
      6
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that acts as a governed customer-support tool, resolving questions only when the knowledge base supports a cited, grounded answer and honestly escalating everything else with provenance and evidence.
      20 PyPI
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables persistent memory, structured thinking sessions, and project-based knowledge management for Claude. It includes specialized coding tools for package discovery and reinvention prevention by validating code against existing libraries and APIs.
      17
      3
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for Google NotebookLM that lets AI agents chat with notebooks, add sources, generate audio overviews, and extract citations via a real Chrome browser.
      MIT

    TDQS

    A4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: notebook CRUD, search/stats, question asking, session lifecycle, and auth/maintenance are separated cleanly. The only notable overlap is setup_auth vs re_auth, though their descriptions do differentiate use cases.

    Naming Consistency5/5

    Tool names consistently follow a snake_case verb_noun pattern: list_notebooks, get_notebook, add_notebook, update_notebook, remove_notebook, search_notebooks, close_session, reset_session. Even the auth tools (setup_auth, re_auth, get_health) and cleanup_data fit the same predictable convention.

    Tool Count4/5

    At 16 tools, the surface is slightly above the ideal range but each tool maps to a real need: notebook library management, question answering, session lifecycle, and authentication/support. The auth/maintenance cluster adds weight, but it is coherent with the server's operational scope.

    Completeness4/5

    The notebook lifecycle is well covered with list/get/add/update/remove/search, plus select, ask_question, and library stats. Minor gaps exist: there is no source-level management and no way to create a brand-new NotebookLM notebook from within the tool set, which are workable limitations.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow