mcp-server-qdrant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QDRANT_URL | No | URL of the Qdrant server (e.g., http://localhost:6333) | |
| QDRANT_API_KEY | No | API key for the Qdrant server | |
| COLLECTION_NAME | No | Name of the default collection to use | |
| EMBEDDING_MODEL | No | Name of the embedding model to use | sentence-transformers/all-MiniLM-L6-v2 |
| QDRANT_READ_ONLY | No | Enable read-only mode (disables qdrant-store tool) | false |
| QDRANT_LOCAL_PATH | No | Path to the local Qdrant database (alternative to QDRANT_URL) | |
| EMBEDDING_PROVIDER | No | Embedding provider to use (currently only 'fastembed' is supported) | fastembed |
| QDRANT_SEARCH_LIMIT | No | Maximum number of results to return from search | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qdrant-findA | Look up memories in Qdrant. Use this tool when you need to:
|
| qdrant-storeB | Keep the memory for later use, when you are asked to remember something. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: qdrant-find for retrieval and qdrant-store for storage. There is no ambiguity between them.
Both tool names follow a consistent pattern with the 'qdrant-' prefix followed by a clear verb ('find', 'store'), making them predictable and easy to understand.
With only 2 tools, the server is minimal but it covers the core operations of storing and retrieving memories. It could benefit from additional tools like delete, but the count is appropriate for a simple memory store.
The server lacks update and delete operations, which are notable gaps for memory management. While store and find cover basic needs, agents may require more functionality for complete lifecycle management.