LABSCO SUMMARY
Nothing leaves the machine, including the embeddings.
Queries are embedded by your own Ollama instance, so neither the question nor the corpus goes to a hosted API — the reason to take a local vector store in the first place. The corresponding limit is that this searches a store; populating it is a separate job, and the bundled script is a search test, not an ingestion pipeline.
What it is
A Node.js vector search server over LanceDB. Queries are embedded locally by Ollama and matched against documents already stored in a LanceDB directory, so both the index and the embedding model stay on your machine.
What you get
- Vector similarity search against stored documents, with results and their similarity scores
- A custom embedding function that calls Ollama and returns embeddings of 768 dimensions, formatted for LanceDB
- A test script you can run before wiring anything up, to confirm the database and the embedding endpoint both answer
Requirements
Node.js v14 or later, a LanceDB storage directory you can read and write, and Ollama running locally with the nomic-embed-text model — the embedding endpoint is http://localhost:11434/api/embeddings. Install with pnpm install. The client launches dist/index.js with node and a --db-path argument pointing at your LanceDB storage. No cloud account and no API key.
Setup effort
Build from source — git clone https://github.com/vurtnec/mcp-LanceDB-node
USE CASES
Searching your own documents without sending them anywhere
Embed the query locally and match against a LanceDB index that never leaves the machine.
Giving an assistant retrieval over a private corpus
Point the server at the storage directory and let the client query it during a conversation.
Checking the pieces line up before integrating
Run the bundled vector-search script to confirm Ollama answers and the table resolves.
BEFORE YOU INSTALL
What to know first
Requires
- Node.js 14 or later
- Ollama running locally with the nomic-embed-text model
- A LanceDB storage directory with read/write permissions
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
git clone https://github.com/vurtnec/mcp-LanceDB-node
cd mcp-LanceDB-node
pnpm install
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"lanceDB": {
"command": "node",
"args": [
"<YOUR_PATH_TO_LANCEDB_NODE>/dist/index.js",
"--db-path",
"<YOUR_PATH_TO_LANCEDB_STORAGE>"
]
}
}
}<YOUR_PATH_TO_LANCEDB_NODE>/dist/index.js is the full path to dist/index.js in your clone (the mcp-LanceDB-node folder), and <YOUR_PATH_TO_LANCEDB_STORAGE> is your LanceDB storage directory.