Head to head · Vector search · October 2026 research run

LanceDB vs Typesense API + MCP

Typesense API + MCP scores 76.6 (BB) on agent readiness against LanceDB's 66.3 (B), and leads in 6 of 7 scored categories. LanceDB leads on maintenance & community. Both do vector search.

Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons

Which one, for what

LanceDB B

Best for Agents whose code can import a library and keep retrieval data in object storage, from notebooks to multimodal datasets.

Ahead on

  • Maintenance & community, 93 against 82

Also in its favour

  • No key needed to call it

Watch for

No self-serve hosted API. Enterprise is sold through a contact form

Typesense API + MCP BB

Best for Retrieval where keyword relevance, typo tolerance, filters and facets matter as much as vectors, and for teams that want a hosted MCP server with tight permissions.

Ahead on

  • Reliability, 83 against 75
  • Schema & documentation, 86 against 81
  • Agent ergonomics, 93 against 74
  • Security & auth, 65 against 44
  • Payments & pricing, 60 against 30

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

Server v30.2 from April 2026 is still the newest stable release

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Typesense API + MCP +30

LanceDB 30

No x402, MPP or L402 (0). The only paid product, Enterprise, sits behind a contact form (0). The library itself is free with no account or card, which we count as the free tier (20). Getting the paid product needs a sales conversation (0). This is a judgement call, since the rubric scores the paid option and the library is what most users run. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Typesense API + MCP 60

No x402, MPP or L402 (0). Hourly pricing by RAM, vCPU, nodes and region through a calculator, bandwidth per GB, no rate table on the page (10). A free-tier cluster (0.5 GB RAM, 2 vCPU burst, one node) needs no payment method (20). Since 28 October an agent connected to the MCP server can create a free-tier cluster before anyone has an account and gets its hostname and a key that can't delete or manage keys, and a person claims the cluster later. A person still clicks "Try it without an account" on the sign-in page in a browser when the client connects, and the other tools need a signed-in account or a management key a person creates, so half, as context-dev's browser-completed claim was read (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth Typesense API + MCP +21

LanceDB 44

The library has no auth of its own and uses the host's object-store credentials. Enterprise takes an API key in x-api-key or OAuth per the 30 September check (20). Least privilege depends on read-only bucket credentials. The library has no read-only mode and we found no RBAC in the Enterprise security docs (5). Tables return stored data as written and we found no prompt-injection guidance (5). No audit log found (0). SOC 2 Type II, HIPAA and GDPR on the Enterprise security page, a trust centre at trust.lancedb.com and a valid security.txt (security@lancedb.com, expires 31 July 2027, re-read on 2 November), but no SECURITY.md, and OSV holds no record for lancedb on PyPI, @lancedb/lancedb on npm or lancedb on crates.io (14). Total 44.

Typesense API + MCP 65

Cluster keys can be limited to collections and actions with an expiry, scoped search keys embed filters, management keys carry named capabilities and the hosted MCP server uses OAuth with consent presets, which would be 30. Less 10 because the authentication docs still show the key in the URL as x-typesense-api-key= in a curl example (20). Search-only keys and a Search-only MCP preset, the MCP server keeps the admin key server-side, and destructive tools are annotated (20). Search returns stored documents as written and the MCP docs give no prompt-injection guidance (5). Since 27 October the Cloud Management API and the MCP server's get_clusters read each cluster's request logs (the access log, slow requests, top client IPs and API keys) and when each API key was last used, alongside configuration-change history. The access log leaves out query strings and bodies. Per-request logs with no audit of key actions, as for deepgram-stt (10). SECURITY.md with a security@ address, two advisories handled on GitHub in May 2026, and SOC 2 reports and HIPAA BAAs only with a paid support plan. No security.txt (404 on 1 November) and no bounty found (10).

Agent ergonomics Typesense API + MCP +19

LanceDB 74

No official MCP server, only a 3-tool reference example, so an agent needs code or its own wrapper (15). select(), limit(), offset(), where() and query types to size and filter results (20). Errors are typed exceptions without documented codes (12). merge_insert gives upserts, and writes create new table versions you can roll back to, but there are no tool annotations to read (12). Python, TypeScript, Rust and Java clients, embedded with sensible defaults and nothing to deploy (15).

Typesense API + MCP 93

10 MCP tools per the docs on 1 November, show_cluster added in October, including two generic read and change tools that cover the rest of the server API (25). per_page, page, include_fields, exclude_fields, filter_by and facets (20). A refused MCP call names the permission it lacks, and imports over 1,000 documents or 10 MB come back as a curl command with a 24-hour key scoped to one collection and action (18). manage_cluster, documents and change_cluster_data are marked destructive so clients ask first. We couldn't confirm readOnlyHint on the read tools (15). Official clients for JavaScript, Python, PHP, Ruby and more. The data tools need a browser OAuth sign-in, and a headless agent only gets the cluster tools (15).

Maintenance & community LanceDB +11

LanceDB 93

v0.41.0 on 29 October 2026 (30). v0.37.1 on 10 August, v0.38.0 on 31 August, v0.39.0 on 17 September, v0.40.0 on 7 October and v0.41.0, with daily betas between them, in the 90 days to 2 November (20). Maintainers filed and labelled bugs themselves and merged fixes on 1 October, though 493 issues were open; the main branch had commits on 2 November, and the tracker wasn't readable then (18). Python, TypeScript, Rust and Java clients ship from one version tag (15). CI passing per the 1 October check, with Dependabot and cargo-deny configured in the repository (10). Total 93.

Typesense API + MCP 82

typesense-python 2.1.1 on 23 October 2026 (30). Since 3 August, typesense-js 3.0.7-1 (31 August), 3.1.0 (25 September), 3.1.1 (5 October) and 3.2.0 (19 October), and typesense-python 2.1.0 (7 October) and 2.1.1 (23 October), so at least three releases in 90 days (20). The server's last stable release is still v30.2, tagged 9 April 2026, and Typesense Cloud lists 31.0 release candidates up to rc23. The v31 branch takes commits daily, but per the 1 October check 805 issues are open and many new ones sit at pre-triage (12). Official clients current with v30 (15). CI runs tests on the server, but the bundled OpenSSL is still pinned at 3.0.5 in WORKSPACE, a branch past end of life (5).

Reliability Typesense API + MCP +8

LanceDB 75

Scored as a local package. Official packages on PyPI, npm and crates.io, with Python 3.10 or later and Node 22 or later stated (20). Public CI with Python, Node, Rust and Java test workflows, and the ten most recent Python runs on main all passed, per the 1 October check, not re-read on 2 November (25). 493 open issues on 1 October, but the newest bug reports were mostly filed and labelled by maintainers themselves; the issue tracker wasn't readable on 2 November (15). Releases follow semver for 0.x. Breaking changes bump the minor version and carry a ! marker, 17 such commits across v0.40.0 and v0.41.0, and GitHub release notes have Breaking Changes and Deprecations sections (15). Still 0.x and not declared stable (0). Total 75.

Typesense API + MCP 83

Instatus page at cloud-status.typesense.org with the management console and 21 cluster regions as components (20). The notice history reports no notices from June to November 2026, and every component shows 100.0 per cent for each month. The last incident was 11 hours 30 minutes of slow new-cluster provisioning on 31 May, with existing clusters unaffected, now outside the 90 days (30). Limits documented with numbers, 300 data calls and 30 cluster actions a minute per MCP connection, 30 a minute per management key, and the docs state there are no HTTP rate limits on the server API (15). The management API returns 429 with "Rate Limit Exceeded. Please try again later.", with no Retry-After or backoff advice. Imports take an upsert action, so a retried import is safe (8 of 15). No SLA found on the pricing page or in the docs we read (0). GA (10).

Schema & documentation Typesense API + MCP +5

LanceDB 81

Typed Python, TypeScript and Rust APIs, and the Lance REST Namespace has an OpenAPI 3.1.1 spec in lance-format/lance-namespace. The docs' own Enterprise OpenAPI link, still listed in llms.txt, returned 404 again on 2 November (20 of 25). llms.txt indexes 235 links to Markdown pages (10). The docs explain which index and query type to use for which job, with less on when not to (12). Typed query builders and schemas, but filters are SQL strings (13). Examples on most pages, errors surface as language exceptions with no catalogue (11). Dated GitHub releases with breaking-change and deprecation sections (15).

Typesense API + MCP 86

OpenAPI 3.0.3 in typesense/typesense-api-spec, 79 operations, version 30.0, last updated 10 September 2026 (25). llms.txt and Markdown docs (10). The MCP docs say whoami should be called first and describe each tool, but we couldn't read the hosted tool definitions themselves (14). The server API is typed in the spec, but two MCP tools, read_cluster_data and change_cluster_data, take any server API path, which leaves the shape to the model (10). An API errors page lists codes 400 to 503, and every docs page has examples in several languages (12). Docs versioned per server release, GitHub releases and a versioned spec (15).

Score by category

CategoryWeightLanceDBTypesense API + MCPEdge
Reliability16%7583Typesense API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8186Typesense API + MCP +5
Agent ergonomics13%7493Typesense API + MCP +19
Security & auth14%4465Typesense API + MCP +21
Payments & pricing10%3060Typesense API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9382LanceDB +11
Transparency & trust7%7579Typesense API + MCP +4
Negative events≤150-2
TotalB 66.3/100BB 76.6/100

Facts side by side

FactLanceDBTypesense API + MCP
KindSDK + MCPHTTP API
VendorLanceDBTypesense
Hosted endpointno (local only)https://cloud.typesense.org/api/v1
TransportsHTTPHTTP, Streamable HTTP
AuthNoneOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0GPL-3.0
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedorg.typesense/typesense-cloud
Last release2026-10-292026-10-23
Terms last updatednot read yetno date given
Privacy policy last updatednot read yetno date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity12k stars, 922k npm/wk, 1.9M PyPI/wk27k stars, 1.1M npm/wk, 276k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

LanceDB

Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.

Typesense API + MCP

Keyword, vector and hybrid search with filters, facets, sorting and geo in one request, with a hosted MCP server that can start a free cluster before an account exists. Server v30.2 from April 2026 is still the newest stable release, and no SLA was found.

Before you call either

LanceDB

  1. Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
  2. Build an FTS index before calling query_type="hybrid", or hybrid search has no keyword side
  3. When reopening a table in a new process, approve its embedding model or endpoint with get_registry().allow_remote_code() or allow_endpoint(), since v0.41.0 refuses settings restored from table metadata
  4. Use select() to drop the vector column from results unless the task needs it
  5. On object storage, set a read consistency interval if several processes write the same table

Typesense API + MCP

  1. Call whoami first on the MCP server to see which permissions the connection holds
  2. Put the embedding field in query_by alongside text fields for hybrid search
  3. Send the key in X-TYPESENSE-API-KEY, not in the URL, so it stays out of logs
  4. Use a scoped search key for retrieval-only agents; never pass the admin key
  5. Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally. Without an account, only free-cluster creation, its status and docs search work

Questions

Which is better for AI agents, LanceDB or Typesense API + MCP?

Typesense API + MCP scores 76.6 (BB) on agent readiness against LanceDB's 66.3 (B), and leads in 6 of 7 scored categories. LanceDB leads on maintenance & community.

Can an agent call LanceDB and Typesense API + MCP without installing anything?

No hosted endpoint is listed for LanceDB. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.

Are LanceDB and Typesense API + MCP open source?

Yes. LanceDB is open source (Apache-2.0). Typesense API + MCP is open source (GPL-3.0).

Other comparisons with LanceDB or Typesense API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.