LanceDB maintains a reference Model Context Protocol server in the lancedb/lancedb-mcp-server repository (linked from lancedb/lancedb issue #2341), implemented with FastMCP and LanceDB embeddings. Tools include `ingest_docs` (embed and store documents), `query_table` (semantic retrieval with configurable top_k and query_type), and `table_details` (schema and row counts) per the README. Configuration uses `uv run lancedb_mcp.py` with environment variables `LANCEDB_URI` (default `~/lancedb`), `TABLE_NAME`, `EMBEDDING_FUNCTION` (default sentence-transformers), and `MODEL_NAME` (default all-MiniLM-L6-v2). The repo describes itself as a basic serverless MCP reference for building more complex LanceDB agent apps—not a full production managed endpoint.
Use cases
- Ingest blog or doc corpora into a local LanceDB table via MCP
- Prototype agentic RAG with sentence-transformer embeddings before production hardening
- Inspect Lance table schemas and row counts from Claude Desktop
- Use as a reference when building custom LanceDB MCP tools for multimodal indexes
- Pair with LanceDB OSS quickstart tables in notebook-to-agent workflows
Key features
- Claude Desktop
- Cursor
- VS Code
Frequently Asked Questions
- Is this LanceDB's only MCP option?
- LanceDB points to this official reference repo; community servers like adiom-data/lance-mcp offer richer catalog/chunk tools separately.
- Where is data stored?
- Defaults to `~/lancedb` via LANCEDB_URI; override TABLE_NAME and embedding settings with env vars.
- Is it production-ready?
- README calls it a basic reference server for ingestion, retrieval, and table details—not a managed cloud MCP.
Related
Related
3 Indexed items
Chroma MCP Server
Chroma documents an official Model Context Protocol server in the chroma-core/chroma-mcp repository and docs.trychroma.com/integrations/frameworks/anthropic-mcp, started with `uvx chroma-mcp` over stdio. Tools include `chroma_list_collections`, `chroma_create_collection`, `chroma_peek_collection`, `chroma_modify_collection`, `chroma_delete_collection`, `chroma_add_documents`, `chroma_query_documents`, `chroma_get_documents`, `chroma_update_documents`, and `chroma_delete_documents` per the README. Client types documented: ephemeral (default), persistent (`--client-type persistent --data-dir`), HTTP self-hosted, and Chroma Cloud (`--client-type cloud` with API keys). Embedding function options include default, Cohere, OpenAI, Jina, VoyageAI, and Roboflow per Chroma MCP docs.
Weaviate MCP Server
Weaviate documents a built-in Model Context Protocol server in the main `weaviate/weaviate` binary from v1.37.1 onward at docs.weaviate.io/weaviate/mcp/mcp-server, exposed as a Streamable HTTP endpoint at `/v1/mcp` on the same port as the REST API (default 8080). Enable with `MCP_SERVER_ENABLED=true`; optional `MCP_SERVER_WRITE_ACCESS_ENABLED=true` registers `weaviate-objects-upsert`. Tools include `weaviate-collections-get-config`, `weaviate-tenants-list`, `weaviate-query-hybrid`, and `weaviate-objects-upsert` (write-gated). Authentication uses existing API keys/Bearer tokens with RBAC permissions `read_mcp`, `create_mcp`, and `update_mcp` per Weaviate 1.37 release notes. The standalone weaviate/mcp-server-weaviate repository is deprecated in favor of this built-in server.
Upstash MCP Server
Upstash documents an official Model Context Protocol server at upstash.com/docs/agent-resources/mcp implemented in the `upstash/mcp-server` repository and npm package `@upstash/mcp-server`. Started with `npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY`, it exposes tools for serverless Redis, QStash, Workflow runs, and Upstash Box so agents can manage and debug account resources from Cursor, Claude Code, VS Code, Codex, and other MCP clients. Read-only API keys automatically disable mutating tools per docs; optional `--transport http`, `--disable-telemetry`, and Upstash Box API key flags are documented for advanced setups.