MCP server for semantic search using local Qdrant vector database and OpenAI embeddings
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"qdrant": {
"args": [
"/path/to/qdrant-mcp-server/build/index.js"
],
"type": "stdio",
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server providing semantic search capabilities using Qdrant vector database with multiple embedding providers.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / search
Web and local search using Brave Search API
Production ready MCP server with real-time search, extract, map & crawl.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
MCP Security Weekly
Get CVE alerts and security updates for Qdrant Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server providing semantic search capabilities using Qdrant vector database with multiple embedding providers.
# Clone and install
git clone https://github.com/mhalder/qdrant-mcp-server.git
cd qdrant-mcp-server
# Node 22.x
npm install
# Node 24.x (requires C++20 flag for native module compilation)
CXXFLAGS='-std=c++20' npm install
# Start services (choose one)
podman compose up -d # Using Podman
docker compose up -d # Using Docker
# Pull the embedding model
podman exec ollama ollama pull nomic-embed-text # Podman
docker exec ollama ollama pull nomic-embed-text # Docker
# Build
npm run build
claude mcp add --transport stdio qdrant -- node /path/to/qdrant-mcp-server/build/index.js
Or add to ~/.claude.json:
{
"mcpServers": {
"qdrant": {
"type": "stdio",
"command": "node",
"args": ["/path/to/qdrant-mcp-server/build/index.js"]
}
}
}
For Qdrant Cloud or secured instances, add --env QDRANT_API_KEY=your-key or set in env config.
Try it:
Create a collection called "notes" and add a document about machine learning
Enable example prompts: Copy prompts.example.json to prompts.json and restart. Use /prompt to list available prompts.
⚠️ Security Warning: When deploying the HTTP transport in production:
- Always run behind a reverse proxy (nginx, Caddy) with HTTPS
- Implement authentication/authorization at the proxy level
- Use firewalls to restrict access to trusted networks
- Never expose directly to the public internet without protection
- Consider implementing rate limiting at the proxy level
- Monitor server logs for suspicious activity
Start the server:
TRANSPORT_MODE=http HTTP_PORT=3000 node build/index.js
Option 1: Using claude mcp add
claude mcp add --transport http qdrant http://your-server:3000/mcp
Option 2: Add to ~/.claude.json
{
"mcpServers": {
"qdrant": {
"type": "http",
"url": "http://your-server:3000/mcp"
}
}
}
Using a different provider:
"env": {
"EMBEDDING_PROVIDER": "ope
... [View full README on GitHub](https://github.com/mhalder/qdrant-mcp-server#readme)