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.
      16,926
      Apache 2.0
    • 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
      C
      maintenance
      Enables MCP-capable agents to search and answer over a local hybrid-retrieval knowledge base as tools, covering querying, grounded answering, index stats, corpus listing, and adding a website. Runs over stdio for local clients or HTTP for remote ones.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for unified full-text search across chat histories from Claude Code, Codex, Cursor CLI, and Antigravity CLI, using SQLite FTS5. Provides read-only tools to search sessions, list conversations, and retrieve session details.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local vector database operations with a Pinecone-compatible API, supporting exact and approximate search, metadata filtering, and semantic text queries over MCP.
      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
    ResponsivenessNo issues