Qdrant MCP Server
MCP : Standardises the connection between an AI application and systems that expose tools or data · requires any-agent
Official Qdrant MCP server: gives Claude, Cursor, or any compatible agent semantic memory, with two actions, storing information and retrieving it by meaning.
The simplest way to connect a Qdrant database to an assistant so it can remember notes, decisions, or code snippets from one session to the next. It requires a Qdrant instance already in place, either local or in the cloud.
Security reflects where data goes, requested permissions and incidents on record at the verification date. It is not a guarantee of zero risk: check the deployment mode and the connections you enable.
What it does, concretely
An AI assistant has no memory between sessions: each conversation starts from scratch. Qdrant MCP Server solves this by providing a persistent semantic memory layer accessible from any MCP-compatible agent.
In practice, the server exposes two actions to the agent: storing information in a Qdrant collection, and retrieving information by the meaning of a natural language query. The default embedding model is sentence-transformers/all-MiniLM-L6-v2, provided via FastEmbed. The collection is created automatically if it does not yet exist.
This tool is aimed at developers using Claude Desktop, Cursor, Windsurf, VS Code, or Claude Code who want their assistant to remember notes, architecture decisions, or code snippets from one session to the next. It can also serve as a semantic search engine over a code snippet database.
It is not suited for someone looking for a turnkey solution without command-line work: configuration is done through environment variables and requires a Qdrant instance already available, locally or in the cloud.
What it offers
- ·Store information in a Qdrant collection via the qdrant-store action, with optional JSON metadata.
- ·Semantic search by natural language via the qdrant-find action, returning up to 10 results by default (configurable).
- ·Automatic collection creation if it does not exist at the time of the first store operation.
- ·Read-only mode activatable via the QDRANT_READ_ONLY variable, which disables the write action.
- ·Customizable tool descriptions via environment variables, to adapt agent behavior to specific contexts (e.g. code search).
- ·Support for three transport protocols: stdio for local use, SSE and streamable-HTTP for remote or shared connections.
- ·Compatible with Claude Desktop, Cursor, Windsurf, VS Code, and Claude Code, as well as any standard MCP client.
- ·Can be deployed via uvx, Docker, or Smithery, with no prior installation needed when using uvx.
In practice
- Price
- Free
- Commercial use
- Commercial use: yes
- Available on
- cli
- Host
- any-agent
- Licence
- Apache 2.0
- FR interface
- No
Security and data
- Rating
- Security: one caveat, see the card
- Your data
- Local or cloud depending on use
- Maintenance
- Active
Links and repository checked on 29 October 2026 · added on 29 October 2026
How to install Qdrant MCP Server
uvx mcp-server-qdrant