qdrant-find
Look up memories in Qdrant. Use this tool when you need to:
- Find memories by their content
- Access memories for further analysis
- Get some personal information about the user
Give an agent one Qdrant collection to write into and search by meaning.
LABSCO SUMMARY
Two calls over one collection: text goes in with whatever metadata you attach and comes back on a described query rather than an exact match. The tool descriptions being configurable is what makes it more than a note store — rewrite them and the same pair becomes the snippet library, the decision log, or whatever else you want the agent to reach for.
Qdrant's own two-call MCP server. One call writes a piece of text, with optional metadata, into a named collection; the other searches that collection in natural language. Embeddings are produced locally by FastEmbed, so no embedding key is involved.
uv, to run uvx mcp-server-qdrant, and somewhere to put the vectors: QDRANT_URL for a running Qdrant, with QDRANT_API_KEY for a managed one, or QDRANT_LOCAL_PATH for an on-disk database. Set one or the other — both together is rejected. EMBEDDING_MODEL defaults to sentence-transformers/all-MiniLM-L6-v2 and only FastEmbed models are supported, so a collection made elsewhere has to match that model's vectors.
One command — uvx mcp-server-qdrant
USE CASES
Write the note when it appears, retrieve it later by describing what it was about rather than remembering how it was worded.
The query is a description, not a keyword, so an entry filed under different wording still comes back.
Rewrite the two tool descriptions so the text field carries what the code does and the metadata carries the code itself.
Start with QDRANT_READ_ONLY set — the store tool is gone from the list, search remains.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
qdrant-findLook up memories in Qdrant. Use this tool when you need to:
qdrant-storeKeep the memory for later use, when you are asked to remember something.
BEFORE YOU INSTALL
2 tools when we connected. Setting QDRANT_READ_ONLY disables qdrant-store, leaving only qdrant-find. Both names use hyphens, not underscores.
uvx on PATH
QDRANT_API_KEY in your environment
CONTEXT COST
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
uvx mcp-server-qdrant{
"mcpServers": {
"qdrant": {
"command": "uvx",
"args": [
"mcp-server-qdrant"
],
"env": {
"QDRANT_URL": "https://xyz-example.eu-central.aws.cloud.qdrant.io:6333",
"QDRANT_API_KEY": "<YOUR_QDRANT_API_KEY>",
"COLLECTION_NAME": "<YOUR_COLLECTION_NAME>",
"EMBEDDING_MODEL": "sentence-transformers/all-MiniLM-L6-v2"
}
}
}
}claude mcp add code-search -e QDRANT_URL="http://localhost:6333" -e COLLECTION_NAME="code-repository" -e EMBEDDING_MODEL="sentence-transformers/all-MiniLM-L6-v2" -- uvx mcp-server-qdrant{
"inputs": [
{
"type": "promptString",
"id": "qdrantUrl",
"description": "Qdrant URL"
},
{
"type": "promptString",
"id": "qdrantApiKey",
"description": "Qdrant API Key",
"password": true
},
{
"type": "promptString",
"id": "collectionName",
"description": "Collection Name"
}
],
"servers": {
"qdrant": {
"command": "uvx",
"args": [
"mcp-server-qdrant"
],
"env": {
"QDRANT_URL": "${input:qdrantUrl}",
"QDRANT_API_KEY": "${input:qdrantApiKey}",
"COLLECTION_NAME": "${input:collectionName}"
}
}
}
}