Skip to main content
Glama
mcpware

notebooklm-api

by mcpware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to notebooklm-api

No user-submitted related servers found.

    Related Servers

    • search-context

      ain3sh
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables semantic search across documentation stored in Gemini FileSearchStores, returning AI-generated answers with source citations.
      1
      -

    • RAG MCP Server

      johnylira
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables document indexing and question answering with Retrieval-Augmented Generation, providing cited answers from user-supplied documents.
      -

    • knowledge_mgmt

      mmaun
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables uploading, organizing, and semantically searching documents with support for various file types and embedding providers.
      6
      MIT

    • RAG Document Server

      jaimeferj
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic search and question-answering over uploaded documents using vector embeddings and Google AI. Supports document organization with tags, section-aware queries, and hierarchical markdown structure preservation.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource action: store creation/listing/deletion, document upload/listing/deletion, and question answering. The 'ask' tool is clearly separated from file management operations, so an agent should not confuse any two tools.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (create_store, list_documents, delete_document). The plural forms in list_stores/list_documents and the bare-verb 'ask' are minor deviations, but they do not undermine readability.

    Tool Count5/5

    Seven tools is a well-scoped size for this document Q&A server. Each tool covers a necessary part of the workflow without redundancy or bloat.

    Completeness4/5

    The store and document lifecycles are mostly covered: create, list, delete, and upload, plus the core ask/search capability. The only noticeable gaps are update/replace operations and a simple get-document detail operation, but these are not critical for the intended workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources