Qdrant API + MCP vs Weaviate API + MCP

Qdrant API + MCP

Database keys can be read-only, limited to chosen collections and expire after 90 days by default. The MCP server has 2 tools, can't manage collections or run filtered queries, and last released on 10 December 2025.

Weaviate API + MCP

Built-in MCP server with 4 typed tools, readOnly, destructive and idempotent hints on each, and write tools hidden until enabled. No public status page or incident history.

Qdrant API + MCP

1. Create payload indexes on the fields you filter on, or filtered search slows on large collections
2. Use /points/query with prefetch to fuse dense and BM25 results
3. Pass wait=true on upserts when the next step reads its own writes
4. On 429, wait for the Retry-After seconds before retrying
5. Set with_vector=false unless the task needs vectors, since they dominate response size

Weaviate API + MCP

1. Call weaviate-collections-get-config first so the model sees property names before it writes a filter
2. weaviate-query-hybrid defaults alpha to 0.75, so lower it for keyword-heavy queries
3. Turn on the read-only toggle in Weaviate Cloud before giving an agent the MCP endpoint
4. Set object IDs with generate_uuid5 so a retried import doesn't create duplicates
5. Free clusters hold one collection. Use tenants rather than extra collections