Skip to main content
Glama
talenlin

notebook-dossier

by talenlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to notebook-dossier

No user-submitted related servers found.

    Related Servers

    • RECON

      rafiulislam4246
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables multi-source research with YouTube, papers, and podcasts, scoring for substance and credibility, and creating NotebookLM notebooks with knowledge graph and feedback loop.
      -

    • NotebookLM MCP Server

      dougrn
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants and agents to connect directly to Google NotebookLM through its high-performance internal RPC calls. Provides grounded RAG chat with citations, notebook and source management (URLs, YouTube, Drive files, text), Audio Overview generation and download, persistent session handling, and automated Deep Research.
      38
      1
      MIT

    • NotebookLM Antigravity AI

      HectorDanielAyarachiFuentes
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive Google NotebookLM notebooks as a deep-research workspace: ingesting local PDFs and YouTube videos, cross-checking sources for contradictions, identifying knowledge gaps, generating audio overviews, and exporting Markdown dossiers with BibTeX and APA bibliographies. It operates over the Model Context Protocol inside Google Antigravity IDE, with browser-session authentication handled automatically.
      MIT

    • io.github.MohdSaleh/tinyfish

      MohdSaleh
      A
      license
      B
      quality
      A
      maintenance
      Enables latency-conscious, auditable deep research by delegating bounded semantic judgments to the calling client LLM while the server owns retrieval, durable state, evidence integrity, citation auditing, and deterministic quality gates.
      20
      MIT

    • NotebookLM MCP Server

      Ronald564
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents and HTTP clients to run citation-backed Q&A against Google NotebookLM notebooks, manage sources, and generate audio, video, infographics, reports, presentations, data tables, flashcards, quizzes and mind maps. Supports multi-account rotation with automatic re-authentication plus a batch/vault pattern for large overnight research runs.
      3,047 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

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct actions: start/status/result/query/import/export/source_get are clearly separable. The fuzziest boundary is between the analysis-producing trio (dossier_compare, dossier_evidence, dossier_query) and the ability to read those same artifacts via dossier_result's views (evidence/comparisons/answers), which requires careful reading of which tool creates versus just retrieves them.

    Naming Consistency4/5

    Strong, predictable snake_case with a uniform 'dossier_' prefix across all ten tools. Minor inconsistency in that several are noun-only state/artifact tools (dossier_status, dossier_result, dossier_auth_status) while others use verbs (dossier_start, dossier_query, dossier_export), but the pattern remains readable.

    Tool Count5/5

    Ten tools is well within the ideal range and each maps to a distinct step in the research lifecycle: launch, poll, read, ask, compare, evidence, import, export, inspect source, check auth. No obvious redundancy or padding in the surface.

    Completeness4/5

    Covers the full lifecycle from dossier_start through status/result, downstream analysis (query/compare/evidence), source inspection, import, and export, with good idempotency hints (request_key). Gaps exist: no way to list or enumerate existing research tasks/notebooks, and no cancel/delete/retry operation, so an agent that loses a research_id has a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources