catalog_searchLABSCO SUMMARY
Retrieval that decides which document before it decides which passage.
Two tables rather than one: summaries to work out where to look, chunks to answer from. That two-step is what keeps a large folder answerable without pushing the whole corpus through the model's context window.
What it is
A Node MCP server over a local LanceDB index of documents you hold on disk. A seed script builds two tables — a catalog of document summaries and a table of vectorised chunks — and the server searches both, so a question can be about the collection as a whole or about one document.
What you get
- Document-level search over the summary catalog, for questions about what the collection contains
- Chunk search scoped to the documents the catalog turned up
- Chunk search across every document at once, for when you do not know where the answer lives
- The index stays on disk on your machine; paired with a local model, nothing goes to the cloud
- Lookups made per question, so the model spends context on what it needs rather than on the corpus
Requirements
Node.js 18+ and npx, plus a local directory to hold the index, passed to the server as its argument. Seeding needs a summarisation model and an embedding model, pulled from Ollama first. The seed script takes the index directory and the documents directory, and can be re-run to rebuild the index from scratch.
Setup effort
Build from source — git clone https://github.com/adiom-data/lance-mcp.git
USE CASES
Working out what a folder of documents actually covers
Search the summary catalog to see which documents exist and what each is about.
Answering a question from one specific report
Find the document in the catalog, then search only its chunks for the passage that answers it.
Finding a passage when you do not know which file it is in
Search every chunk at once and let the match point at the document.
Working over material that cannot leave the machine
Query the local index with a local model, so both the documents and the questions stay on disk.
3 tools
Listed in project docs. Your client may show a different list.
chunks_searchall_chunks_searchBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
- Ollama, with the summarisation and embedding models pulled
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
git clone https://github.com/adiom-data/lance-mcp.git
cd lance-mcp
npm install
ollama pull snowflake-arctic-embed2
ollama pull llama3.1:8bCreate a local directory to hold the index, then seed it from your documents: npm run seed -- --dbpath <YOUR_DBPATH> --filesdir <YOUR_FILESDIR> (rerun with --overwrite to rebuild it)
MCP Clients
Claude Desktop
{
"mcpServers": {
"lancedb": {
"command": "npx",
"args": [
"lance-mcp",
"<YOUR_PATH_TO_LOCAL_INDEX_DIR>"
]
}
}
}<YOUR_PATH_TO_LOCAL_INDEX_DIR> is the index directory you seeded.