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 | |
| 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 |
| FASTMCP_LOG_LEVEL | No | Set logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | INFO |
| 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 |
| FASTMCP_SERVER_HOST | No | Host address to bind the server to | 127.0.0.1 |
| FASTMCP_SERVER_PORT | No | Port to run the server on | 8000 |
| QDRANT_SEARCH_LIMIT | No | Maximum number of results to return from search | 10 |
| FASTMCP_SERVER_DEBUG | No | Enable debug mode | false |
| TOOL_FIND_DESCRIPTION | No | Custom description for the find tool | |
| TOOL_STORE_DESCRIPTION | No | Custom description for the store tool | |
| FASTMCP_SERVER_DEPENDENCIES | No | List of dependencies to install in the server environment | [] |
| FASTMCP_SERVER_ON_DUPLICATE_TOOLS | No | Behavior for duplicate tools (warn, error, replace, ignore) | warn |
| FASTMCP_SERVER_ON_DUPLICATE_PROMPTS | No | Behavior for duplicate prompts (warn, error, replace, ignore) | warn |
| FASTMCP_SERVER_ON_DUPLICATE_RESOURCES | No | Behavior for duplicate resources (warn, error, replace, ignore) | warn |
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 retrieves memories while qdrant-store saves them. There is no overlap or ambiguity between them.
Both tools follow the same 'qdrant-<verb>' pattern, using lowercase snake case. The verb clearly indicates the action (find vs. store), making the naming predictable and consistent.
With only two tools, the server feels minimal for a memory system. While find and store cover basic operations, the count is borderline and could easily support more operations like delete or list.
The tool surface covers create (store) and read (find) but lacks update and delete operations for memories. This is a notable gap for a complete lifecycle, though the core functionality works.