Qdrant MCP: Not existing vector name error (named vs unnamed vector mismatch)
Fixes the Qdrant MCP server failing to store or search with Not existing vector name error. The collection uses named vectors but the server expects a different vector name (or vice versa). The fix is aligning the server's configured vector name with the collection. Use when the collection exists but store/search fail; not for connection errors.
TL;DR: Not existing vector name means the collection's vector layout does not match what the MCP server expects. Named vs unnamed vectors are getting mixed up. Check the collection's vector config and align the server's expected vector name with it.
Not existing vector name errorFix it
- Inspect the collection's vector configuration:
curl -H "api-key value YOUR_KEY" your-cluster/collections/your-collection | python3 -m json.tool | grep -A 10 vectors Look for whether vectors is a single config (unnamed) or a map of names (named vectors).
- Compare with what the MCP server is configured to use. The server settings (e.g. vector name, embedding provider output) must match the collection.
- Fix the mismatch one of two ways:
- Point the server at the collection's actual vector name, or
- Recreate the collection with the layout the server expects, then re-index.
- Restart the MCP server.
Expected: store and search operations succeed.
When to use this
- The collection exists and is reachable, but store/search fail with the vector name error.
- The collection was created by a different tool than the MCP server.
When NOT to use this
- The error is collection not found. That is a name problem, not a vector-layout problem.
- Connection or auth errors. Fix those first.
Compatibility
- qdrant/mcp-server-qdrant and compatible forks with configurable vector names.
- Qdrant collections with named vectors (multi-vector setups).
Why it happens
Qdrant supports both unnamed vectors (one per point) and named vectors (several per point, e.g. dense plus sparse). The MCP server was configured against one layout, but the collection was created with the other, often by a different tool or an earlier server version. The names do not line up, so every vector operation misses.
Edge cases
- Recreating the collection deletes its data. Export or re-index afterward.
- Embedding dimension must also match. A 1536-dim vector into a 768-dim collection fails differently but is worth checking at the same time.
- If multiple tools share the collection, agree on one vector naming scheme across all of them.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.