Qdrant MCP Server
A Model Context Protocol (MCP) server providing semantic search capabilities using Qdrant vector database with multiple embedding providers.
에이전트 강화
게시자가 제공하는 설치 방식입니다. PlugMCP 엔드포인트가 아닙니다.
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행# 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": "openai", // or "cohere", "voyage"
"OPENAI_API_KEY": "sk-...", // provider-specific API key
"QDRANT_URL": "http://localhost:6333"
}
Restart after making changes.
See Advanced Configuration section below for all options.
qdrant://collections - List all collectionsqdrant://collection/{name} - Collection detailsCreate custom prompts tailored to your specific use cases without modifying code. Prompts provide guided workflows for common tasks.
Note: By default, the server looks for prompts.json in the project root directory. If the file exists, prompts are automatically loaded. You can specify a custom path using the PROMPTS_CONFIG_FILE environment variable.
Create a prompts configuration file (e.g., prompts.json in the project root):
See prompts.example.json for example configurations you can copy and customize.
Configure the server (optional - only needed for custom path):
If you place prompts.json in the project root, no additional configuration is needed. To use a custom path:
{
"mcpServers": {
"qdrant": {
"command": "node",
"args": ["/path/to/qdrant-mcp-server/build/index.js"],
"env": {
"QDRANT_URL": "http://localhost:6333",
"PROMPTS_CONFIG_FILE": "/custom/path/to/prompts.json"
}
}
}
}
Claude Code:
/mcp__qdrant__find_similar_docs papers "neural networks" 10
VSCode:
/mcp.qdrant.find_similar_docs papers "neural networks" 10
See prompts.example.json for ready-to-use prompts including:
setup_rag_collection - Create RAG-optimized collectionsanalyze_and_optimize - Collection insights and recommendationscompare_search_strategies - Semantic vs hybrid search comparisonmigrate_to_hybrid - Collection migration guidedebug_search_quality - Troubleshoot poor search resultsbuild_knowledge_base - Structured documentation with metadataindex_git_history - Index repository commit history for semantic searchsearch_project_history - Search git history to understand feature implementationsinvestigate_code_with_history - Deep dive into code with contextual searchcross_repo_search - Search patterns across multiple repositoriestrace_feature_evolution - Track how features evolved over timesecurity_audit_search - Find security-related code and fixesTemplates use {{variable}} placeholders:
Intelligently index and search your codebase using semantic code search. Perfect for AI-assisted development, code exploration, and understanding large codebases.
1. Index your codebase:
# Via Claude Code MCP tool
/mcp__qdrant__index_codebase /path/to/your/project
2. Search your code:
# Natural language search
/mcp__qdrant__search_code /path/to/your/project "authentication middleware"
# Filter by file type
/mcp__qdrant__search_code /path/to/your/project "database schema" --fileTypes .ts,.js
# Filter by path pattern
/mcp__qdrant__search_code /path/to/your/project "API endpoints" --pathPattern src/api/**
3. Update after changes:
# Incrementally re-index only changed files
/mcp__qdrant__reindex_changes /path/to/your/project
// The MCP tool automatically:
// 1. Scans all .ts, .tsx, .js, .jsx files
// 2. Respects .gitignore patterns (skips node_modules, dist, etc.)
// 3. Chunks code at function/class boundaries
// 4. Generates embeddings using your configured provider
// 5. Stores in Qdrant with metadata (file path, line numbers, language)
index_codebase({
path: "/workspace/my-app",
forceReindex: false, // Set to true to re-index from scratch
});
// Output:
// ✓ Indexed 247 files (1,823 chunks) in 45.2s
search_code({
path: "/workspace/my-app",
query: "how does user authentication work?",
limit: 5,
});
// Results include file path, line numbers, and code snippets:
// [
// {
// filePath: "src/auth/middleware.ts",
// startLine: 15,
// endLine: 42,
// content: "export async function authenticateUser(req: Request) { ... }",
// score: 0.89,
// language: "typescript"
// },
// ...
// ]
// Only search TypeScript files
search_code({
path: "/workspace/my-app",
query: "error handling patterns",
fileTypes: [".ts", ".tsx"],
limit: 10,
});
// Only search in specific directories
search_code({
path: "/workspace/my-app",
query: "API route handlers",
pathPattern: "src/api/**",
limit: 10,
});
// After making changes to your codebase
reindex_changes({
path: "/workspace/my-app",
});
// Output:
// ✓ Updated: +3 files added, ~5 files modified, -1 files deleted
// ✓ Chunks: +47 added, -23 deleted in 8.3s
get_index_status({
path: "/workspace/my-app",
});
// Output:
// {
// status: "indexed", // "not_indexed" | "indexing" | "indexed"
// isIndexed: true, // deprecated: use status instead
// collectionName: "code_a3f8d2e1",
// chunksCount: 1823,
// filesCount: 247,
// lastUpdated: "2025-01-30T10:15:00Z",
// languages: ["typescript", "javascript", "json"]
// }
Programming Languages (35+ file types):
See configuration for full list and customization options.
Create a .contextignore file in your project root to specify additional patterns to ignore:
# .contextignore
**/test/**
**/*.test.ts
**/*.spec.ts
**/fixtures/**
**/mocks/**
**/__tests__/**
index_codebase for initial indexing, then reindex_changes for updatesfileTypes and pathPattern for better resultsget_index_status to verify a codebase is indexed before searchingTypical performance on a modern laptop (Apple M1/M2 or similar):
Note: Indexing time varies based on embedding provider. Ollama (local) is fastest for initial indexing.
Index and search your repository's git commit history using natural language. Perfect for finding past fixes, understanding change patterns, and learning from previous work.
1. Index your repository's git history:
# Via Claude Code MCP tool
/mcp__qdrant__index_git_history /path/to/your/repo
2. Search for relevant commits:
# Natural language search
/mcp__qdrant__search_git_history /path/to/your/repo "fix authentication bug"
# Filter by commit type
/mcp__qdrant__search_git_history /path/to/your/repo "database optimization" --commitTypes fix,perf
# Filter by author
/mcp__qdrant__search_git_history /path/to/your/repo "API changes" --authors "[email protected]"
3. Keep index up to date:
# Incrementally index only new commits
/mcp__qdrant__index_new_commits /path/to/your/repo
Combine code and git history search for deeper codebase understanding. Requires repositories to be indexed with both index_codebase and index_git_history first.
See Advanced Search Examples for detailed usage, workflows, and scenarios.
See examples/ directory for detailed guides:
Note: Ollama models require pulling before use:
podman exec ollama ollama pull <model-name>docker exec ollama ollama pull <model-name>npm run dev # Development with auto-reload
npm run build # Production build
npm run type-check # TypeScript validation
npm test # Run test suite
npm run test:coverage # Coverage report
771 tests across 28 test files with 97%+ coverage:
CI/CD: GitHub Actions runs build, type-check, and tests on Node.js 22.x and 24.x for every push/PR.
Contributions welcome! See CONTRIBUTING.md for:
feat:, fix:, BREAKING CHANGE:)npm test, npm run type-check, npm run build)Automated releases: Semantic versioning via conventional commits - feat: → minor, fix: → patch, BREAKING CHANGE: → major.
The code vectorization feature is inspired by and builds upon concepts from the excellent claude-context project (MIT License, Copyright 2025 Zilliz).
MIT - see LICENSE file.
MCP server for semantic search using local Qdrant vector database and OpenAI embeddings
도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Qdrant은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-10-28. MCP server for semantic search using local Qdrant vector database and OpenAI embeddings