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 a MCP server for Qdrant, a vector search engine.
An official 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
qdrant-find
Environment Variables
The configuration of the server is done using environment variables:
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
Note: You cannot provide both QDRANT_URL and QDRANT_LOCAL_PATH at the same time.
[!IMPORTANT]
Command-line arguments are not supported anymore! Please use environment variables for all configuration.
Installation
Using uvx
When using `uvx` no specific installation is needed to directly run mcp-server-qdrant.
Transport Protocols
The server supports different transport protocols that can be specified using the --transport flag:
Supported transport protocols:
stdio (default): Standard input/output transport, might only be used by local MCP clients
sse: Server-Sent Events transport, perfect for remote clients
The default transport is stdio if not specified.
Using Docker
A Dockerfile is available for building and running the MCP server:
Installing via Smithery
To install Qdrant MCP Server for Claude Desktop automatically via Smithery:
Manual configuration of 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:
For local Qdrant mode:
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.
For the time being, only FastEmbed models are supported.
Support for other tools
This MCP server can be used with any MCP-compatible client. For example, you can use it with
Cursor and VS Code, which provide built-in support for the Model Context
Protocol.
Using with Cursor/Windsurf
You can configure this MCP server to work as a code search tool for Cursor or Windsurf by customizing the tool
descriptions:
In Cursor/Windsurf, you can then configure the MCP server in your settings by pointing to this running server using
SSE transport protocol. The description on how to add an MCP server to Cursor can be found in the Cursor
documentation. If you are
running Cursor/Windsurf locally, you can use the following URL:
[!TIP]
We suggest SSE transport as a preferred way to connect Cursor/Windsurf to the MCP server, as it can support remote
connections. That makes it easy to share the server with your team or use it in a cloud environment.
This configuration transforms the Qdrant MCP server into a specialized code search tool that can:
Store code snippets, documentation, and implementation details
Retrieve relevant code examples based on semantic search
Help developers find specific implementations or usage patterns
You can populate the database by storing natural language descriptions of code snippets (in the information parameter)
along with the actual code (in the metadata.code property), and then search for them using natural language queries
that describe what you're looking for.
[!NOTE]
The tool descriptions provided above are examples and may need to be customized for your specific use case. Consider
adjusting the descriptions to better match your team's workflow and the specific types of code snippets you want to
store and retrieve.
If you have successfully installed the `mcp-server-qdrant`, but still can't get it to work with Cursor, please
consider creating the [Cursor rules](https://docs.cursor.com/context/rules-for-ai) so the MCP tools are always used when
the agent produces a new code snippet. You can restrict the rules to only work for certain file types, to avoid using
the MCP server for the documentation or other types of content.
Using with Claude Code
You can enhance Claude Code's capabilities by connecting it to this MCP server, enabling semantic search over your
existing codebase.
Setting up mcp-server-qdrant
Add the MCP server to Claude Code:
Verify the server was added:
Using Semantic Code Search in Claude Code
Tool descriptions, specified in TOOL_STORE_DESCRIPTION and TOOL_FIND_DESCRIPTION, guide Claude Code on how to use
the MCP server. The ones provided above are examples and may need to be customized for your specific use case. However,
Claude Code should be already able to:
Use the qdrant-store tool to store code snippets with descriptions.
Use the qdrant-find tool to search for relevant code snippets using natural language.
Run MCP server in Development Mode
The MCP server can be run in development mode using the mcp dev command. This will start the server and open the MCP
inspector in your browser.
Using with VS Code
For one-click installation, click one of the install buttons below:
Add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).
Or if you prefer using Docker, add this configuration instead:
Alternatively, you can create a .vscode/mcp.json file in your workspace with the following content:
For workspace configuration with Docker, use this in .vscode/mcp.json:
Contributing
If you have suggestions for how mcp-server-qdrant could be improved, or want to report a bug, open an issue!
We'd love all and any contributions.
Testing `mcp-server-qdrant` locally
The MCP inspector is a developer tool for testing and debugging MCP
servers. It runs both a client UI (default port 5173) and an MCP proxy server (default port 3000). Open the client UI in
your browser to use the inspector.
Once started, open your browser to http://localhost:5173 to access the inspector interface.
License
This MCP server is licensed under the Apache License 2.0. This means you are free to use, modify, and distribute the
software, subject to the terms and conditions of the Apache License 2.0. For more details, please see the LICENSE file
in the project repository.
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 a MCP server for Qdrant, a vector search engine.
An official 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
qdrant-find
Environment Variables
The configuration of the server is done using environment variables:
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
Note: You cannot provide both QDRANT_URL and QDRANT_LOCAL_PATH at the same time.
[!IMPORTANT]
Command-line arguments are not supported anymore! Please use environment variables for all configuration.
Installation
Using uvx
When using `uvx` no specific installation is needed to directly run mcp-server-qdrant.
Transport Protocols
The server supports different transport protocols that can be specified using the --transport flag:
Supported transport protocols:
stdio (default): Standard input/output transport, might only be used by local MCP clients
sse: Server-Sent Events transport, perfect for remote clients
The default transport is stdio if not specified.
Using Docker
A Dockerfile is available for building and running the MCP server:
Installing via Smithery
To install Qdrant MCP Server for Claude Desktop automatically via Smithery:
Manual configuration of 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:
For local Qdrant mode:
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.
For the time being, only FastEmbed models are supported.
Support for other tools
This MCP server can be used with any MCP-compatible client. For example, you can use it with
Cursor and VS Code, which provide built-in support for the Model Context
Protocol.
Using with Cursor/Windsurf
You can configure this MCP server to work as a code search tool for Cursor or Windsurf by customizing the tool
descriptions:
In Cursor/Windsurf, you can then configure the MCP server in your settings by pointing to this running server using
SSE transport protocol. The description on how to add an MCP server to Cursor can be found in the Cursor
documentation. If you are
running Cursor/Windsurf locally, you can use the following URL:
[!TIP]
We suggest SSE transport as a preferred way to connect Cursor/Windsurf to the MCP server, as it can support remote
connections. That makes it easy to share the server with your team or use it in a cloud environment.
This configuration transforms the Qdrant MCP server into a specialized code search tool that can:
Store code snippets, documentation, and implementation details
Retrieve relevant code examples based on semantic search
Help developers find specific implementations or usage patterns
You can populate the database by storing natural language descriptions of code snippets (in the information parameter)
along with the actual code (in the metadata.code property), and then search for them using natural language queries
that describe what you're looking for.
[!NOTE]
The tool descriptions provided above are examples and may need to be customized for your specific use case. Consider
adjusting the descriptions to better match your team's workflow and the specific types of code snippets you want to
store and retrieve.
If you have successfully installed the `mcp-server-qdrant`, but still can't get it to work with Cursor, please
consider creating the [Cursor rules](https://docs.cursor.com/context/rules-for-ai) so the MCP tools are always used when
the agent produces a new code snippet. You can restrict the rules to only work for certain file types, to avoid using
the MCP server for the documentation or other types of content.
Using with Claude Code
You can enhance Claude Code's capabilities by connecting it to this MCP server, enabling semantic search over your
existing codebase.
Setting up mcp-server-qdrant
Add the MCP server to Claude Code:
Verify the server was added:
Using Semantic Code Search in Claude Code
Tool descriptions, specified in TOOL_STORE_DESCRIPTION and TOOL_FIND_DESCRIPTION, guide Claude Code on how to use
the MCP server. The ones provided above are examples and may need to be customized for your specific use case. However,
Claude Code should be already able to:
Use the qdrant-store tool to store code snippets with descriptions.
Use the qdrant-find tool to search for relevant code snippets using natural language.
Run MCP server in Development Mode
The MCP server can be run in development mode using the mcp dev command. This will start the server and open the MCP
inspector in your browser.
Using with VS Code
For one-click installation, click one of the install buttons below:
Add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).
Or if you prefer using Docker, add this configuration instead:
Alternatively, you can create a .vscode/mcp.json file in your workspace with the following content:
For workspace configuration with Docker, use this in .vscode/mcp.json:
Contributing
If you have suggestions for how mcp-server-qdrant could be improved, or want to report a bug, open an issue!
We'd love all and any contributions.
Testing `mcp-server-qdrant` locally
The MCP inspector is a developer tool for testing and debugging MCP
servers. It runs both a client UI (default port 5173) and an MCP proxy server (default port 3000). Open the client UI in
your browser to use the inspector.
Once started, open your browser to http://localhost:5173 to access the inspector interface.
License
This MCP server is licensed under the Apache License 2.0. This means you are free to use, modify, and distribute the
software, subject to the terms and conditions of the Apache License 2.0. For more details, please see the LICENSE file
in the project repository.