qdrant-kuzu-mcp
# qdrant-kuzu-mcp: A Qdrant MCP server
[](https://smithery.ai/protocol/qdrant-kuzu-mcp)
> The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) 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 extends the official Qdrant MCP server ([qdrant/mcp-server-qdrant](https://github.com/qdrant/mcp-server-qdrant),
pinned upstream commit in [`UPSTREAM_PIN`](UPSTREAM_PIN)) with Kuzu-backed graph traversal tools, turning it into a
unified Graph-RAG memory layer: vector similarity search via Qdrant, entity-relationship traversal via the embedded
[Kuzu](https://github.com/kuzudb/kuzu) graph database.
## Overview
An official Model Context Protocol server for keeping and retrieving memories in the Qdrant vector search engine,
extended with an entity graph stored in Kuzu. It acts as a semantic memory layer on top of the Qdrant database:
memories are stored as vectors, and the entities and relations they mention are recorded in a Kuzu graph that can
be traversed alongside similarity search.
## Components
### Tools
1. `qdrant-store`
- Store some information in the Qdrant database
- Input:
- `information` (string): Information to store
- `metadata` (JSON): Optional metadata to store
- `entities` (list of strings): Optional entity names mentioned by the information; recorded in the Kuzu entity graph and linked to this memory (only available when the graph layer is enabled and writable)
- `relations` (list of objects): Optional entity relations, each `{subject, predicate, object}` with snake_case predicates (e.g. `depends_on`); endpoints are created implicitly (only available when the graph layer is enabled and writable)
- `collection_name` (string): Name of the collection to store the information in. This field is required if there are no default collection name.
If there is a default collection name, this field is not enabled.
- Returns: Confirmation message
2. `qdrant-find`
- Retrieve relevant information from the Qdrant database
- Input:
- `query` (string): Query to use for searching
- `collection_name` (string): Name of the collection to store the information in. This field is required if there are no default collection name.
If there is a default collection name, this field is not enabled.
- Returns: Information stored in the Qdrant database as separate messages
3. `qdrant-graph-find` (requires the `graph` extra)
- Traverse the entity graph derived from stored memories
- Input:
- `entity` (string): Seed entity name to expand from
- `relation` (string): Optional relation kind filter (snake_case)
- `depth` (int): Maximum hops from the seed, 1-3, default 1
- `direction` (string): `any`, `out`, or `in`, default `any`
- `limit` (int): Maximum entities returned, 1-100, default 20
- Returns: JSON envelope with seed info, related entities (with hop distance and relation kind), and a referencing chunk per entity
4. `qdrant-graph-expand-from-hits` (requires the `graph` extra)
- Search memories in Qdrant, then expand the entity graph from the entities those memories mention (via their `metadata.entities`)
- Input:
- `query` (string): Query for the vector search
- `collection_name` (string): Collection to search
- `relation`, `depth`, `limit`: As in `qdrant-graph-find`
- `search_limit` (int): How many Qdrant hits to harvest entities from, 1-10, default 5
- Returns: JSON envelope with per-seed graph expansions
> The graph tools are registered only when the Kuzu layer is available (package installed, `KUZU_ENABLED` not `false`,
> and the database opens successfully). If Kuzu is unavailable the server degrades gracefully to the upstream
> two-tool surface; the upstream tools are never removed or renamed.
## Environment Variables
Configuration is done via environment variables. The only command-line argument is `--transport`, used to select the [transport protocol](#transport-protocols).
> [!NOTE]
> You cannot provide both `QDRANT_URL` and `QDRANT_LOCAL_PATH` at the same time.
| Name | Description | Default Value |
|--------------------------|---------------------------------------------------------------------|-------------------------------------------------------------------|
| `QDRANT_URL` | URL of the Qdrant server | None |
| `QDRANT_API_KEY` | API key for the Qdrant server | None |
| `COLLECTION_NAME` | Name of the default collection to use. | None |
| `QDRANT_LOCAL_PATH` | Path to the local Qdrant database (alternative to `QDRANT_URL`) | None |
| `EMBEDDING_PROVIDER` | Embedding provider to use (currently only "fastembed" is supported) | `fastembed` |
| `EMBEDDING_MODEL` | Name of the embedding model to use | `sentence-transformers/all-MiniLM-L6-v2` |
| `TOOL_STORE_DESCRIPTION` | Custom description for the store tool | See default in [`settings.py`](src/qdrant_kuzu_mcp/settings.py) |
| `TOOL_FIND_DESCRIPTION` | Custom description for the find tool | See default in [`settings.py`](src/qdrant_kuzu_mcp/settings.py) |
| `QDRANT_SEARCH_LIMIT` | Maximum number of results to return from search | `10` |
| `QDRANT_READ_ONLY` | Enable read-only mode (disables `qdrant-store` tool) | `false` |
### Kuzu graph layer
The graph layer is active when the `kuzu` package is installed (install with the `graph` extra, see
[Installation](#installation)) and `KUZU_ENABLED` is not `false`. If the Kuzu database cannot be opened, the
server logs a warning and starts with the upstream two-tool surface only.
| Name | Description | Default Value |
|-----------------------------|--------------------------------------------------------------------------------|---------------|
| `KUZU_ENABLED` | Force the graph layer off without uninstalling the extra | `true` |
| `KUZU_DB_PATH` | Path to the embedded Kuzu database directory. `:memory:` for a per-process in-memory graph | `./kuzu_db` |
| `KUZU_READ_ONLY` | Open Kuzu read-only: graph read tools stay, `entities`/`relations` write params are hidden | `false` |
| `KUZU_BUFFER_POOL_SIZE` | Kuzu buffer pool size in bytes (0 = engine default) | `536870912` |
| `KUZU_MAX_CONCURRENT_QUERIES` | Max concurrent Kuzu read queries | `4` |
### FastMCP Environment Variables
Since `qdrant-kuzu-mcp` is based on FastMCP, it also supports all the FastMCP environment variables. The most
important ones are listed below:
| Environment Variable | Description | Default Value |
|--------------------------------------------|-----------------------------------------------------------------|---------------|
| `FASTMCP_LOG_LEVEL` | Set logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | `INFO` |
| `FASTMCP_SERVER_DEBUG` | Enable debug mode | `false` |
| `FASTMCP_SERVER_HOST` | Host address to bind the server to | `127.0.0.1` |
| `FASTMCP_SERVER_PORT` | Port to run the server on | `8000` |
| `FASTMCP_SERVER_ON_DUPLICATE_RESOURCES` | Behavior for duplicate resources (warn, error, replace, ignore) | `warn` |
| `FASTMCP_SERVER_ON_DUPLICATE_TOOLS` | Behavior for duplicate tools (warn, error, replace, ignore) | `warn` |
| `FASTMCP_SERVER_ON_DUPLICATE_PROMPTS` | Behavior for duplicate prompts (warn, error, replace, ignore) | `warn` |
| `FASTMCP_SERVER_DEPENDENCIES` | List of dependencies to install in the server environment | `[]` |
> [!NOTE]
> Server-specific settings use the `FASTMCP_SERVER_` prefix. This may change in future versions.
## Installation
### Using uv / uvx
Create a virtualenv and install with the graph extra (recommended, includes Kuzu):
```shell
uv venv
uv pip install -e ".[graph]"
```
Or without the graph layer (vector tools only, matches the upstream surface):
```shell
uv venv
uv pip install -e .
```
Run the server (stdio transport by default):
```shell
QDRANT_URL="http://localhost:6333" \
COLLECTION_NAME="my-collection" \
KUZU_DB_PATH="./kuzu_db" \
python -m qdrant_kuzu_mcp
```
### Using pip
```shell
python -m venv .venv
# Windows: .venv\Scripts\activate — Linux/macOS: source .venv/bin/activate
pip install -e ".[graph]"
python -m qdrant_kuzu_mcp
```
### Quick local check (no external services)
With a local embedded Qdrant and an on-disk Kuzu database — both backends run embedded, nothing to deploy:
```shell
QDRANT_LOCAL_PATH="./qdrant_storage" \
COLLECTION_NAME="memories" \
KUZU_DB_PATH="./kuzu_db" \
python -m qdrant_kuzu_mcp
```
Then send an MCP `initialize` + `tools/list` request over stdio; you should see all four tools:
`qdrant-find`, `qdrant-store`, `qdrant-graph-find`, `qdrant-graph-expand-from-hits`.
### Using uvx
When using [`uvx`](https://docs.astral.sh/uv/guides/tools/#running-tools) no specific installation is needed to directly run *qdrant-kuzu-mcp*.
```shell
QDRANT_URL="http://localhost:6333" \
COLLECTION_NAME="my-collection" \
EMBEDDING_MODEL="sentence-transformers/all-MiniLM-L6-v2" \
uvx qdrant-kuzu-mcp
```
#### Transport Protocols
The server supports different transport protocols that can be specified using the `--transport` flag:
```shell
QDRANT_URL="http://localhost:6333" \
COLLECTION_NAME="my-collection" \
uvx qdrant-kuzu-mcp --transport sse
```
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
- `streamable-http`: Streamable HTTP transport, perfect for remote clients, more recent than SSE
The default transport is `stdio` if not specified.
When SSE transport is used, the server will listen on the specified port and wait for incoming connections. The default
port is 8000, however it can be changed using the `FASTMCP_SERVER_PORT` environment variable.
```shell
QDRANT_URL="http://localhost:6333" \
COLLECTION_NAME="my-collection" \
FASTMCP_SERVER_PORT=1234 \
uvx qdrant-kuzu-mcp --transport sse
```
### Using Docker
A Dockerfile is available for building and running the MCP server:
```bash
# Build the container
docker build -t qdrant-kuzu-mcp .
# Run the container
docker run -p 8000:8000 \
-e FASTMCP_SERVER_HOST="0.0.0.0" \
-e QDRANT_URL="http://your-qdrant-server:6333" \
-e QDRANT_API_KEY="your-api-key" \
-e COLLECTION_NAME="your-collection" \
qdrant-kuzu-mcp
```
> [!TIP]
> Please note that we set `FASTMCP_SERVER_HOST="0.0.0.0"` to make the server listen on all network interfaces. This is
> necessary when running the server in a Docker container.
### Installing via Smithery
To install Qdrant MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/protocol/qdrant-kuzu-mcp):
```bash
npx @smithery/cli install qdrant-kuzu-mcp --client claude
```
### 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`:
```json
{
"qdrant": {
"command": "uvx",
"args": ["qdrant-kuzu-mcp"],
"env": {
"QDRANT_URL": "https://xyz-example.eu-central.aws.cloud.qdrant.io:6333",
"QDRANT_API_KEY": "your_api_key",
"COLLECTION_NAME": "your-collection-name",
"EMBEDDING_MODEL": "sentence-transformers/all-MiniLM-L6-v2"
}
}
}
```
For local Qdrant mode:
```json
{
"qdrant": {
"command": "uvx",
"args": ["qdrant-kuzu-mcp"],
"env": {
"QDRANT_LOCAL_PATH": "/path/to/qdrant/database",
"COLLECTION_NAME": "your-collection-name",
"EMBEDDING_MODEL": "sentence-transformers/all-MiniLM-L6-v2"
}
}
}
```
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](https://qdrant.github.io/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](https://docs.cursor.com/context/model-context-protocol) and [VS Code](https://code.visualstudio.com/docs), 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:
```bash
QDRANT_URL="http://localhost:6333" \
COLLECTION_NAME="code-snippets" \
TOOL_STORE_DESCRIPTION="Store reusable code snippets for later retrieval. \
The 'information' parameter should contain a natural language description of what the code does, \
while the actual code should be included in the 'metadata' parameter as a 'code' property. \
The value of 'metadata' is a Python dictionary with strings as keys. \
Use this whenever you generate some code snippet." \
TOOL_FIND_DESCRIPTION="Search for relevant code snippets based on natural language descriptions. \
The 'query' parameter should describe what you're looking for, \
and the tool will return the most relevant code snippets. \
Use this when you need to find existing code snippets for reuse or reference." \
uvx qdrant-kuzu-mcp --transport sse # Enable SSE transport
```
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](https://docs.cursor.com/context/model-context-protocol#adding-an-mcp-server-to-cursor). If you are
running Cursor/Windsurf locally, you can use the following URL:
```
http://localhost:8000/sse
```
> [!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:
1. Store code snippets, documentation, and implementation details
2. Retrieve relevant code examples based on semantic search
3. 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 `qdrant-kuzu-mcp`, 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 qdrant-kuzu-mcp
1. Add the MCP server to Claude Code:
```shell
# Add qdrant-kuzu-mcp configured for code search
claude mcp add code-search \
-e QDRANT_URL="http://localhost:6333" \
-e COLLECTION_NAME="code-repository" \
-e EMBEDDING_MODEL="sentence-transformers/all-MiniLM-L6-v2" \
-e TOOL_STORE_DESCRIPTION="Store code snippets with descriptions. The 'information' parameter should contain a natural language description of what the code does, while the actual code should be included in the 'metadata' parameter as a 'code' property." \
-e TOOL_FIND_DESCRIPTION="Search for relevant code snippets using natural language. The 'query' parameter should describe the functionality you're looking for." \
-- uvx qdrant-kuzu-mcp
```
2. Verify the server was added:
```shell
claude mcp list
```
#### 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:
1. Use the `qdrant-store` tool to store code snippets with descriptions.
2. 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.
```shell
COLLECTION_NAME=mcp-dev fastmcp dev src/qdrant_kuzu_mcp/server.py
```
### Using with VS Code
For one-click installation, click one of the install buttons below:
[](https://insiders.vscode.dev/redirect/mcp/install?name=qdrant&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22qdrant-kuzu-mcp%22%5D%2C%22env%22%3A%7B%22QDRANT_URL%22%3A%22%24%7Binput%3AqdrantUrl%7D%22%2C%22QDRANT_API_KEY%22%3A%22%24%7Binput%3AqdrantApiKey%7D%22%2C%22COLLECTION_NAME%22%3A%22%24%7Binput%3AcollectionName%7D%22%7D%7D&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantUrl%22%2C%22description%22%3A%22Qdrant+URL%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantApiKey%22%2C%22description%22%3A%22Qdrant+API+Key%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22collectionName%22%2C%22description%22%3A%22Collection+Name%22%7D%5D) [](https://insiders.vscode.dev/redirect/mcp/install?name=qdrant&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22qdrant-kuzu-mcp%22%5D%2C%22env%22%3A%7B%22QDRANT_URL%22%3A%22%24%7Binput%3AqdrantUrl%7D%22%2C%22QDRANT_API_KEY%22%3A%22%24%7Binput%3AqdrantApiKey%7D%22%2C%22COLLECTION_NAME%22%3A%22%24%7Binput%3AcollectionName%7D%22%7D%7D&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantUrl%22%2C%22description%22%3A%22Qdrant+URL%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantApiKey%22%2C%22description%22%3A%22Qdrant+API+Key%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22collectionName%22%2C%22description%22%3A%22Collection+Name%22%7D%5D&quality=insiders)
[](https://insiders.vscode.dev/redirect/mcp/install?name=qdrant&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-p%22%2C%228000%3A8000%22%2C%22-i%22%2C%22--rm%22%2C%22-e%22%2C%22QDRANT_URL%22%2C%22-e%22%2C%22QDRANT_API_KEY%22%2C%22-e%22%2C%22COLLECTION_NAME%22%2C%22qdrant-kuzu-mcp%22%5D%2C%22env%22%3A%7B%22QDRANT_URL%22%3A%22%24%7Binput%3AqdrantUrl%7D%22%2C%22QDRANT_API_KEY%22%3A%22%24%7Binput%3AqdrantApiKey%7D%22%2C%22COLLECTION_NAME%22%3A%22%24%7Binput%3AcollectionName%7D%22%7D%7D&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantUrl%22%2C%22description%22%3A%22Qdrant+URL%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantApiKey%22%2C%22description%22%3A%22Qdrant+API+Key%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22collectionName%22%2C%22description%22%3A%22Collection+Name%22%7D%5D) [](https://insiders.vscode.dev/redirect/mcp/install?name=qdrant&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-p%22%2C%228000%3A8000%22%2C%22-i%22%2C%22--rm%22%2C%22-e%22%2C%22QDRANT_URL%22%2C%22-e%22%2C%22QDRANT_API_KEY%22%2C%22-e%22%2C%22COLLECTION_NAME%22%2C%22qdrant-kuzu-mcp%22%5D%2C%22env%22%3A%7B%22QDRANT_URL%22%3A%22%24%7Binput%3AqdrantUrl%7D%22%2C%22QDRANT_API_KEY%22%3A%22%24%7Binput%3AqdrantApiKey%7D%22%2C%22COLLECTION_NAME%22%3A%22%24%7Binput%3AcollectionName%7D%22%7D%7D&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantUrl%22%2C%22description%22%3A%22Qdrant+URL%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22qdrantApiKey%22%2C%22description%22%3A%22Qdrant+API+Key%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22collectionName%22%2C%22description%22%3A%22Collection+Name%22%7D%5D&quality=insiders)
#### Manual Installation
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)`.
```json
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "qdrantUrl",
"description": "Qdrant URL"
},
{
"type": "promptString",
"id": "qdrantApiKey",
"description": "Qdrant API Key",
"password": true
},
{
"type": "promptString",
"id": "collectionName",
"description": "Collection Name"
}
],
"servers": {
"qdrant": {
"command": "uvx",
"args": ["qdrant-kuzu-mcp"],
"env": {
"QDRANT_URL": "${input:qdrantUrl}",
"QDRANT_API_KEY": "${input:qdrantApiKey}",
"COLLECTION_NAME": "${input:collectionName}"
}
}
}
}
}
```
Or if you prefer using Docker, add this configuration instead:
```json
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "qdrantUrl",
"description": "Qdrant URL"
},
{
"type": "promptString",
"id": "qdrantApiKey",
"description": "Qdrant API Key",
"password": true
},
{
"type": "promptString",
"id": "collectionName",
"description": "Collection Name"
}
],
"servers": {
"qdrant": {
"command": "docker",
"args": [
"run",
"-p", "8000:8000",
"-i",
"--rm",
"-e", "QDRANT_URL",
"-e", "QDRANT_API_KEY",
"-e", "COLLECTION_NAME",
"qdrant-kuzu-mcp"
],
"env": {
"QDRANT_URL": "${input:qdrantUrl}",
"QDRANT_API_KEY": "${input:qdrantApiKey}",
"COLLECTION_NAME": "${input:collectionName}"
}
}
}
}
}
```
Alternatively, you can create a `.vscode/mcp.json` file in your workspace with the following content:
```json
{
"inputs": [
{
"type": "promptString",
"id": "qdrantUrl",
"description": "Qdrant URL"
},
{
"type": "promptString",
"id": "qdrantApiKey",
"description": "Qdrant API Key",
"password": true
},
{
"type": "promptString",
"id": "collectionName",
"description": "Collection Name"
}
],
"servers": {
"qdrant": {
"command": "uvx",
"args": ["qdrant-kuzu-mcp"],
"env": {
"QDRANT_URL": "${input:qdrantUrl}",
"QDRANT_API_KEY": "${input:qdrantApiKey}",
"COLLECTION_NAME": "${input:collectionName}"
}
}
}
}
```
For workspace configuration with Docker, use this in `.vscode/mcp.json`:
```json
{
"inputs": [
{
"type": "promptString",
"id": "qdrantUrl",
"description": "Qdrant URL"
},
{
"type": "promptString",
"id": "qdrantApiKey",
"description": "Qdrant API Key",
"password": true
},
{
"type": "promptString",
"id": "collectionName",
"description": "Collection Name"
}
],
"servers": {
"qdrant": {
"command": "docker",
"args": [
"run",
"-p", "8000:8000",
"-i",
"--rm",
"-e", "QDRANT_URL",
"-e", "QDRANT_API_KEY",
"-e", "COLLECTION_NAME",
"qdrant-kuzu-mcp"
],
"env": {
"QDRANT_URL": "${input:qdrantUrl}",
"QDRANT_API_KEY": "${input:qdrantApiKey}",
"COLLECTION_NAME": "${input:collectionName}"
}
}
}
}
```
## Contributing
If you have suggestions for how qdrant-kuzu-mcp could be improved, or want to report a bug, open an issue!
We'd love all and any contributions.
### Testing `qdrant-kuzu-mcp` locally
The [MCP inspector](https://github.com/modelcontextprotocol/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.
```shell
QDRANT_URL=":memory:" COLLECTION_NAME="test" \
fastmcp dev src/qdrant_kuzu_mcp/server.py
```
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.
## Privacy and support
- [Privacy Policy](https://qdrant.tech/legal/privacy-policy/)
- [Support](https://github.com/qdrant/qdrant-kuzu-mcp/issues)
TDQS
Scored across 2 tools
The two tools are exact opposites — one stores, one retrieves — so there is no possibility of confusing their purposes. Each tool's role is clear from its name and description.
Both tools follow the same verb-oriented convention with a consistent 'qdrant-' prefix: qdrant-find and qdrant-store. The pattern is uniform and predictable.
At two tools, the server is on the thin side — it covers the bare minimum but feels underdeveloped for a memory system that could reasonably include more operations. The count is borderline rather than egregiously incomplete.
The basic store-and-retrieve lifecycle is present, but there are notable gaps: no way to delete, update, list all memories, or search by metadata. Agents can work around this, but the surface is minimal and lacks full memory management.