feat: add support for unnamed vectors in Qdrant collections #78
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for unnamed vectors in Qdrant collections, allowing the MCP server to work with existing Qdrant databases that use the default vector field instead of named vector fields.
Problem
When using Qdrant collections created with unnamed vectors (common when using embeddings like Google Gemini), the MCP server would fail with the error:
Solution
USE_UNNAMED_VECTORS
environment variable that enables unnamed vector supportUnnamedVectorProvider
wrapper class that signals to use unnamed vectorsQdrantConnector
to handle both named and unnamed vector operationsUsage
To use with unnamed vectors, simply set the environment variable:
Testing
The changes maintain backward compatibility - existing users with named vectors will see no change. Only users who explicitly enable
USE_UNNAMED_VECTORS=true
will use the new functionality.Related Issues
This addresses user feedback about incompatibility with existing Qdrant collections that use unnamed vectors.
🤖 Generated with Claude Code