Qdrant Server
A semantic memory layer that stores and retrieves information using the Qdrant vector search engine. It enables storing memories and finding relevant information through semantic search.
The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.
This repository is an example of how to create an MCP server for Qdrant, a vector search engine.
Overview
A basic Model Context Protocol server for keeping and retrieving memories in the Qdrant vector search engine. It acts as a semantic memory layer on top of the Qdrant database.
Components
Tools
-
qdrant-store-memory
- Store a memory in the Qdrant database
- Input:
information
(string): Memory to store
- Returns: Confirmation message
-
qdrant-find-memories
- Retrieve a memory from the Qdrant database
- Input:
query
(string): Query to retrieve a memory
- Returns: Memories stored in the Qdrant database as separate messages
Usage with Claude Desktop
To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json
:
Replace http://localhost:6333
, your_api_key
, and your_collection_name
with your Qdrant server URL, Qdrant API key, and collection name, respectively. The use of the API key is optional, but recommended for security reasons, depending on the Qdrant server configuration.
This MCP server will automatically create a collection with the specified name if it doesn't exist.
By default, the server will use the sentence-transformers/all-MiniLM-L6-v2
embedding model to encode memories. Currently, only FastEmbed models are supported, and you can change it by passing the --fastembed-model-name
argument to the server.
Using the Local Mode of Qdrant
To use a local mode of Qdrant, you can specify the path to the database using the --qdrant-local-path
argument:
It will run Qdrant local mode inside the same process as the MCP server. Although it is not recommended for production.