Head to head · Vector search · October 2026 research run

LanceDB vs Pinecone API + MCP

Pinecone API + MCP scores 79.3 (A) on agent readiness against LanceDB's 66.3 (B), and leads in 6 of 7 scored categories. 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.

Also in its favour

  • No key needed to call it
  • Open source

Watch for

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

Pinecone API + MCP A

Best for Teams that want a hosted index with nothing to run, hosted embedding and reranking, and a versioned API agents can rely on.

Ahead on

  • Reliability, 80 against 75
  • Schema & documentation, 94 against 81
  • Agent ergonomics, 83 against 74
  • Security & auth, 79 against 44
  • Payments & pricing, 60 against 30
  • Transparency & trust, 84 against 75

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Serverless reads in AWS us-west-2 returned 5xx errors for 11 hours on 17 September 2026

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.

Security & auth Pinecone API + MCP +35

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.

Pinecone API + MCP 79

API keys are per project with roles, and the Admin API uses OAuth service accounts with client credentials (30). Key roles allow read-only access and deletion protection guards indexes, but the MCP server has no read-only mode (18). Stored records come back as written and we found no prompt-injection guidance (5). Audit logs are listed on the security page and in the trust centre (12). SOC 2 Type II, HIPAA with a BAA and ISO 27001, which the trust centre at security.pinecone.io says passed its annual ISO 27001:2022 surveillance audit (posted 1 April 2026), plus a SECURITY.md in the MCP repo. No security.txt (404 on 1 November) and no bug bounty found (14).

Payments & pricing Pinecone 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.

Pinecone API + MCP 60

No x402, MPP or L402 (0). Per-unit prices for storage, read and write units, egress, import and backup are public, re-read on 1 November, and the rate-limit page lists the monthly caps per plan (20). Starter is free with no card (20). A person signs up in the browser to get a key. Service accounts need an existing organisation (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Pinecone API + MCP +13

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).

Pinecone API + MCP 94

OpenAPI files per API version in pinecone-io/pinecone-api, twelve for 2026-07 covering control, data, inference, admin, Assistant and Nexus, plus a proto file, re-read on 1 November (25). llms.txt and Markdown docs (10). MCP descriptions say what each tool does, when to call describe-index first, and when a tool fails, for example search "only works with integrated-inference indexes", and they carry a freshness warning (18). Zod schemas with enums for cloud and rerank model and validated record fields, but filter is a free-form object (13). An error-handling guide and examples throughout the docs (13). Dated API versions released quarterly and a dated changelog (15).

Agent ergonomics Pinecone API + MCP +9

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).

Pinecone API + MCP 83

12 MCP tools in v0.4.0 (29 October), up from 9, after three document-index tools were added, so 11 to 30 tools (15). Every database tool also carries two optional analytics fields, llm_provider and llm_model, each with about 500 characters of description, which adds context cost for no task benefit (less 5, so 10). topK, metadata filters, field selection, rerank topN and pagination tokens on list calls (20). Documented error codes, and MCP errors are written for the model, such as "Do not retry. Ask the user to create an API key" (18). Every tool sets readOnlyHint, the two upsert tools set destructiveHint and idempotentHint, and the two create tools are marked idempotent and not destructive (20). Few required fields and official clients for Python, TypeScript, Java, Go and .NET (15). 10+20+18+20+15 = 83.

Transparency & trust Pinecone API + MCP +9

LanceDB 75

Apache-2.0 (30). Terms and privacy are PDFs on a HubSpot file host. The terms name the vendor only as Company, the privacy PDF names LanceDB Systems, Inc., and the Enterprise docs say customer data stays in the customer's account (15). Release notes carry a Deprecations section and breaking changes bump the minor version, but there's no notice period (12). No telemetry module in the open-source library source, and the Enterprise docs limit telemetry to system health (18).

Pinecone API + MCP 84

Closed service with published terms. The MCP server and clients are Apache-2.0 (18). The privacy policy dates from 8 May 2024 and gives no retention period beyond "as long as necessary". A public Data Processing Addendum dated 24 May 2024, linked from pinecone.io/legal, commits to deletion on termination, SCCs, security-incident notice without undue delay and a named Subprocessor List (20). Quarterly API versions, each supported for at least 12 months with at least nine months to migrate. Calls without a version header fall to the oldest supported version. Pinecone Local, the Docker emulator, reached end of life on 7 October with no earlier deprecation entry found in the 2025 or 2026 changelog, but it sits outside the listed API and MCP server (20). Regions per cloud are listed, and the DPA promises update notices before a new subprocessor and 15 days to object. The trust centre's Subprocessor List, which our reader couldn't load on 6 October, was read on 17 October. It has nine entries, each with a purpose and a location, among them Google and two other cloud providers ("USA and customer-selected cloud regions"), Confluent, Pylon, Salesforce and Twilio in the USA, and affiliates in Israel and the UK, so 20 rather than 14 (20).

Reliability Pinecone API + MCP +5

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.

Pinecone API + MCP 80

Atlassian Statuspage at status.pinecone.io with per-cloud, per-region components and incident history back to June 2026 in its RSS feed (20). Re-read on 1 November, seven incidents fall in the 90 days from 3 August and none is posted after 14 October. The 20 and 21 July incidents have left the window. On 17 September the read path of serverless indexes in AWS us-west-2 returned 5xx errors for 11 hours 7 minutes (05:37 to 16:44 UTC), which reads as one major in one region, as qdrant's and temporal's regional outages were read. The others read as partial by this run's rule. On 1 September "5xx errors on some control plane operations" ran 4 hours 36 minutes ("likely related to ongoing issues in GCP"). On 7 October newly created indexes failed to initialise in GCP us-central1 for 1 hour 9 minutes. On 22 and 23 September "a small percentage of read requests" failed in AWS eu-west-1 for about an hour. A pod write failure on 28 September, 21 minutes of read and write 5xx in GCP us-central1 on 25 August, and inference 5xx on 14 October were shorter or narrower. Statuspage itself marks 1 September, 17 September and 7 October as major. One major, so 10 (5 on 17 October, which counted every incident over an hour). Limits published with numbers, 100 requests a second per namespace and 2,000 read units a second per index, plus monthly caps per plan, re-read on 1 November (15). 429 TOO_MANY_REQUESTS with exponential backoff guidance, though no Retry-After. Upserts overwrite by ID, so a retried write is safe (15). 99.95% uptime SLA on Enterprise (10). GA (10). 20+10+15+15+10+10 = 80.

Score by category

CategoryWeightLanceDBPinecone API + MCPEdge
Reliability16%7580Pinecone API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8194Pinecone API + MCP +13
Agent ergonomics13%7483Pinecone API + MCP +9
Security & auth14%4479Pinecone API + MCP +35
Payments & pricing10%3060Pinecone API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9390LanceDB +3
Transparency & trust7%7584Pinecone API + MCP +9
Negative events≤150-2
TotalB 66.3/100A 79.3/100

Facts side by side

FactLanceDBPinecone API + MCP
KindSDK + MCPHTTP API
VendorLanceDBPinecone
Hosted endpointno (local only)https://api.pinecone.io
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthNoneAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0proprietary (MCP server Apache-2.0)
Tools exposednone12
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-292026-10-29
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/wk71 stars, 928k npm/wk, 970k PyPI/wk
Agent reviews3/5 (2)3.5/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Pinecone API + MCP higher.

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.

Pinecone API + MCP

OpenAPI files per API version, quarterly versions with at least 12 months of support each. Serverless reads in AWS us-west-2 returned 5xx errors for 11 hours on 17 September 2026, among seven regional or partial incidents since August.

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

Pinecone API + MCP

  1. Send X-Pinecone-Api-Version: 2026-07 on every call. Without it you get the oldest supported version
  2. Queries go to the index host from describe_index, not to api.pinecone.io
  3. Wait a few seconds and retry when fresh upserts don't show up in search
  4. Back off exponentially on 429. There's no Retry-After header
  5. Starter blocks reads once egress or read units run out for the month, so a failing agent may just be out of quota. Pinecone Local is gone, so test against a separate project
  6. Run the MCP server on Node.js 22 or later from v0.4.0, and use the document-index tools for full-text search

Questions

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

Pinecone API + MCP scores 79.3 (A) on agent readiness against LanceDB's 66.3 (B), and leads in 6 of 7 scored categories.

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

No hosted endpoint is listed for LanceDB. Pinecone API + MCP has a hosted endpoint at https://api.pinecone.io.

Are LanceDB and Pinecone API + MCP open source?

LanceDB is open source (Apache-2.0). No open-source release is listed for Pinecone API + MCP.

Other comparisons with LanceDB or Pinecone 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.