Qdrant API + MCP vs Vespa

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.

Vespa

Vespa Cloud publishes hourly unit prices, a 99.5% uptime agreement for paying customers and a trial with $300 of credits and no card. Every call needs an application package deployed first, no OpenAPI file was found in the reviewed documentation, and Vespa.ai says it has no official public MCP server.

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

Vespa

1. Deploy an application package with a schema before feeding or querying. Use vespa deploy and wait for the endpoint to report ready
2. Send a token as Authorization: Bearer only to the endpoint marked Token. The mTLS endpoint needs the client certificate and key
3. Set hits, offset and presentation.summary on queries. hits is capped at 400 by default and the query timeout defaults to 0.5s
4. On 429 from /document/v1 reduce the feed rate and back off. On 507 stop feeding, because the cluster is out of memory or disk
5. Use the condition parameter for test-and-set writes and expect 412 when it fails or the document is missing