LanceDB MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ingest_docsC | |
| query_tableC | |
| table_detailsB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: ingesting documents, querying a table, and retrieving table details. No overlap exists.
All tool names follow a consistent verb_noun pattern (ingest_docs, query_table, table_details) using snake_case.
Three tools is minimal but appropriate for a basic LanceDB server covering ingestion, querying, and metadata inspection. Slightly limited but not unreasonable.
Covers core operations (ingest, query, details) but lacks delete, update, or list tables, which are notable gaps for a database server.