Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1
Prepare the server locally
Run this once before adding it to Claude Code.
git clone https://github.com/ChrisGVE/workspace-qdrant-mcp
cd workspace-qdrant-mcpThen follow the repository README for any remaining dependency or build steps.
2
Register it in Claude Code
claude mcp add -e "QDRANT_URL=${QDRANT_URL}" workspace-qdrant -- node /path/to/workspace-qdrant-mcp/src/typescript/mcp-server/dist/index.jsReplace any placeholder paths in the command with the real path on your machine.
Required:
QDRANT_URL3
Make your agent remember this setup
workspace-qdrant's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Hybrid search combining semantic similarity and keyword matching via Reciprocal Rank Fusion
- Automatic Git repository awareness and project-scoped collections
- Tree-sitter semantic chunking for deep code intelligence
- Relationship graph analysis including PageRank and community detection
- Background daemon (memexd) for continuous file monitoring and indexing
Tools 6
searchPerforms hybrid semantic and keyword search across the indexed project.retrieveRetrieves specific content or context from the indexed workspace.rulesManages persistent behavioral rules for the AI assistant.storeStores new findings, analysis, or design rationale for future retrieval.grepPerforms keyword-based searching within the project files.listLists indexed files or collections within the workspace.Environment Variables
QDRANT_URLrequiredThe URL of the running Qdrant instanceTry it
→Search for the implementation details of the authentication module in the current project.
→Store this design rationale about the new database schema for future reference.
→List all files related to the API integration to get an overview of the structure.
→Find any existing rules regarding code style or project architecture.
Original README from ChrisGVE/workspace-qdrant-mcp
workspace-qdrant-mcp
Project-scoped vector database for AI assistants, providing hybrid semantic + keyword search with automatic project detection.
Features
- Hybrid Search - Combines semantic similarity with keyword matching using Reciprocal Rank Fusion
- Project Detection - Automatic Git repository awareness and project-scoped collections
- 6 MCP Tools - search, retrieve, rules, store, grep, list
- Code Intelligence - Tree-sitter semantic chunking + LSP integration for active projects
- Code Graph - Relationship graph with algorithms (PageRank, community detection, betweenness centrality)
- High-Performance CLI - Rust-based
wqmcommand-line tool - Background Daemon -
memexdfor continuous file monitoring and processing
Quick Start
Prerequisites
- Qdrant -
docker run -d -p 6333:6333 -v qdrant_storage:/qdrant/storage qdrant/qdrant - C compiler - Required for compiling Tree-sitter grammars on first use. Tree-sitter grammars are distributed as C source and compiled locally.
- macOS:
xcode-select --install(Xcode Command Line Tools) - Linux:
apt install build-essential(Debian/Ubuntu) ordnf groupinstall "Development Tools"(Fedora) - Windows: Install Visual Studio Build Tools with C++ workload
- macOS:
Install
Option 1: Homebrew (Recommended — macOS & Linux)
brew install ChrisGVE/tap/workspace-qdrant
brew services start workspace-qdrant
Option 2: Pre-built Binaries
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/ChrisGVE/workspace-qdrant-mcp/main/scripts/download-install.sh | bash
# Windows (PowerShell)
irm https://raw.githubusercontent.com/ChrisGVE/workspace-qdrant-mcp/main/scripts/download-install.ps1 | iex
Installs wqm and memexd to ~/.local/bin (Linux/macOS) or %LOCALAPPDATA%\wqm\bin (Windows).
Option 3: Build from Source
git clone https://github.com/ChrisGVE/workspace-qdrant-mcp.git
cd workspace-qdrant-mcp
./install.sh
See Installation Reference for detailed instructions and platform-specific notes. For Windows, see the Windows Installation Guide.
Configure MCP
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"workspace-qdrant-mcp": {
"command": "node",
"args": ["/path/to/workspace-qdrant-mcp/src/typescript/mcp-server/dist/index.js"],
"env": {
"QDRANT_URL": "http://localhost:6333"
}
}
}
}
Claude Code:
claude mcp add workspace-qdrant-mcp -- node /path/to/workspace-qdrant-mcp/src/typescript/mcp-server/dist/index.js
Verify
wqm --version
wqm admin health
CLAUDE.md Integration
Add the following to your project's CLAUDE.md (or your global ~/.claude/CLAUDE.md) so Claude Code uses workspace-qdrant proactively:
## workspace-qdrant
The `workspace-qdrant` MCP server provides codebase-aware search, a library knowledge base, a scratchpad for accumulated insights, and persistent behavioral rules. The tool schemas are self-describing; these instructions cover *when* and *how* to use them.
### Primary Search and Knowledge Base
**Use `workspace-qdrant` first whenever context is uncertain** — first session on a project, returning after a significant gap, or exploring an unfamiliar subsystem. It is faster and more accurate than walking files manually, and it retrieves findings from prior sessions that would otherwise be lost.
**Three-step protocol:**
1. **Search** with `workspace-qdrant` (`search`, `grep`, `list`, or `retrieve`)
2. **Fall back** to `Grep`, `Glob`, `WebSearch` only when workspace-qdrant is insufficient or unavailable
3. **Store** any new findings, analysis, or design rationale via `store` so they are retrievable in future sessions
When a fresh handover or strong prior context already covers what you need, skip the exploratory search — but always store new findings at the end.
**Collections and their purpose:**
- `projects` — indexed codebase; use `scope="project"` (current project) or `scope="all"` (across all proj