Skip to main content
Glama

Related Servers

Alternatives to Lancelot

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to query locally indexed code, docs, logs, JSONL/CSV and PDFs using BM25 full-text, vector and hybrid search, returning cited passages with file:line references instead of whole-file reads. Also supports code search, batch queries and persistent agent memory namespaces.
      19,151
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP hosts to perform air-gapped, CPU-only hybrid semantic and BM25 keyword search over indexed PDFs, Markdown, and text files through a local LanceDB store, with root-jailed indexing and optional read-only locking.
      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
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables local-first hybrid BM25 and vector retrieval over project documentation and code through an MCP stdio interface, returning retrieved text with provenance as data rather than instructions.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude Code and Cursor to search a documentation corpus, read specific pages, and locally ask grounded questions with verified citations over stdio or Streamable HTTP.
      MIT

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation3/5

    lancedb_search and lancedb_query have overlapping retrieval purposes; an agent could easily pick the wrong one without careful reading. The descriptions distinguish them somewhat (raw search vs RAG context retrieval), but the boundary is not crisp. Status and version are clearly distinct.

    Naming Consistency5/5

    All four tools use a consistent lancedb_<verb/noun> prefix pattern. Names are readable and predictable throughout.

    Tool Count4/5

    Four tools is on the thin side but reasonable for a focused retrieval/status server. No obvious bloat, though the surface feels minimal.

    Completeness2/5

    The surface only covers search/query/status/version; there is no way to create or ingest documents, list tables, update, or delete data. For a LanceDB server, these are significant lifecycle gaps that would force agents to fail on write/admin tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data