Skip to main content
Glama
glucero0

nl-file-search

by glucero0

Related Servers

Alternatives to nl-file-search

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables local AI agents to perform hybrid search (BM25 + vector) over privately indexed local files, including notes, PDFs, DOCX, source code, and OCR'd images. All indexing and retrieval stay on the machine with read-only, whitelist-scoped access.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search any local folder through a private SQLite FTS5 index that extracts text from PDFs, Office documents, plain text, code and zip listings, returning ranked matches instead of slow ls/grep scans. It also supports metadata and glob listing, paged retrieval of already-extracted text, duplicate detection, and incremental background re-indexing with secrets and caches excluded by default.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables local-first hybrid knowledge retrieval from authorized Markdown and plain-text files, combining full-text and vector search with reranking and traceable source references via a single search tool.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables any MCP client to index files, directories, and arbitrary text into a local SQLite-backed vector database and perform semantic search with language-aware chunking, filters, and context expansion, all offline without network calls.
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides local semantic search over files using embeddings, enabling directory indexing and natural language queries without external services.
      50 PyPI
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    search_files and get_file have clearly distinct roles: search finds indexed files by natural language, while get_file retrieves content or metadata for a path returned by search. The descriptions reinforce this boundary by explicitly telling users to pass paths from search_files and not to use get_file for arbitrary disk paths.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun snake_case pattern: search_files and get_file. The singular/plural difference mirrors the operation, and the naming is predictable and readable.

    Tool Count4/5

    Two tools are slightly below the typical 3-15 range, but they form a focused search-then-retrieve workflow. The scope is narrow enough that each tool earns its place without bloat.

    Completeness4/5

    The server covers the core lifecycle of finding indexed files and retrieving their indexed content or media metadata. Minor gaps remain around index management or broader listing, but these may be intentionally handled by the companion nl-search ingestion system.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues