qdrant-memory-mcp 0.1.0__py3-none-any.whl

qdrant_memory_mcp-0.1.0.dist-info/METADATA

@@ -0,0 +1,173 @@
+Metadata-Version: 2.4
+Name: qdrant-memory-mcp
+Version: 0.1.0
+Summary: Metadata-only stdio MCP distribution of the Qdrant Memory Runtime
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/cnkang/qdrant-memory-mcp
+Project-URL: Repository, https://github.com/cnkang/qdrant-memory-mcp
+Project-URL: Issues, https://github.com/cnkang/qdrant-memory-mcp/issues
+Project-URL: Changelog, https://github.com/cnkang/qdrant-memory-mcp/blob/main/CHANGELOG.md
+Project-URL: Runtime, https://github.com/cnkang/hermes-plugin-qdrant-memory
+Project-URL: Skill, https://github.com/cnkang/skills/tree/main/qdrant-memory
+Keywords: mcp,memory,qdrant,agents
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: hermes-plugin-qdrant-memory[mcp]==0.2.0
+Dynamic: license-file
+
+# Qdrant Memory MCP
+
+<!-- mcp-name: io.github.cnkang/qdrant-memory -->
+
+[简体中文](README.zh-CN.md)
+
+Persistent, scoped memory for AI agents through four explicit **stdio MCP** tools.
+This repository distributes the existing [Python Runtime](https://github.com/cnkang/hermes-plugin-qdrant-memory).
+Its metadata-only wheel contains no Python business implementation. The console
+script points directly to `qdrant_memory.standalone:main` and depends on
+`hermes-plugin-qdrant-memory[mcp]==0.2.0`.
+
+**Versions:** MCP distribution 0.1.0 depends on Runtime 0.2.0. Release artifacts
+are available through the [distribution PyPI page](https://pypi.org/project/qdrant-memory-mcp/)
+and [Runtime PyPI page](https://pypi.org/project/hermes-plugin-qdrant-memory/).
+See [release checklist](docs/publishing.md) for the publishing sequence.
+
+Runtime, [optional Agent Skill](https://github.com/cnkang/skills/tree/main/qdrant-memory)
+and MCP distribution versions are independent. The Skill is usage guidance,
+not a runtime dependency. Hermes retains its native MemoryProvider, automatic
+extraction and prefetch. Ordinary MCP performs only explicitly requested memory
+operations; it does not automatically extract every conversation turn.
+
+## Install and initialize
+
+Requires Python 3.11+ and either [uv](https://docs.astral.sh/uv/) or a Python
+virtual environment. You must configure storage and an embedding service.
+For the example below, run Ollama and install `qwen3-embedding:4b` yourself.
+
+Create an operator-owned profile directory and save `qdrant-memory.json` inside:
+
+```json
+{
+  "schema_version": 1,
+  "scope": {"user_id": "my-user", "agent_id": "my-agent"},
+  "qdrant": {"mode": "embedded", "collection": "qdrant_memory"},
+  "embedding": {
+    "mode": "plugin", "provider": "ollama", "model": "qwen3-embedding:4b",
+    "base_url": "http://127.0.0.1:11434", "dimensions": 2560, "distance": "Cosine"
+  }
+}
+```
+
+Initialize, then launch (replace `/path/to/profile` with your absolute path):
+
+```bash
+uvx --from qdrant-memory-mcp==0.1.0 qdrant-memory-mcp --home /path/to/profile init
+uvx --from qdrant-memory-mcp==0.1.0 qdrant-memory-mcp --home /path/to/profile mcp
+```
+
+The command without `--home` uses `~/.qdrant-memory`, independent of Hermes.
+Configure and initialize that directory before letting a Registry client launch
+`uvx qdrant-memory-mcp==0.1.0 mcp`. The executable name matches the package name;
+the Registry's positional `mcp` selects protocol mode. Its optional named
+`--home` precedes `mcp` when a client supplies a custom profile.
+
+Alternatively:
+
+```bash
+python3 -m venv .venv
+.venv/bin/python -m pip install qdrant-memory-mcp==0.1.0
+.venv/bin/qdrant-memory-mcp --home /path/to/profile init
+.venv/bin/qdrant-memory-mcp --home /path/to/profile mcp
+```
+
+On Windows use `.venv\Scripts\python.exe` and
+`.venv\Scripts\qdrant-memory-mcp.exe`.
+
+Qdrant embedded, self-hosted server and Cloud, plus Ollama and OpenAI-compatible
+embeddings, are configured in the Runtime's [configuration reference](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/configuration.md).
+Keep credentials in operator environment variables (`QDRANT_API_KEY`,
+`EMBEDDING_API_KEY`, or configured names); never commit their values.
+Initialization against an existing collection requires explicit operator choice;
+do not use a production destination for a first test.
+
+## Connect a client
+
+Codex `config.toml` example:
+
+```toml
+[mcp_servers.qdrant_memory]
+command = "uvx"
+args = ["--from", "qdrant-memory-mcp==0.1.0", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
+```
+
+OpenCode `opencode.json` example:
+
+```json
+{
+  "$schema": "https://opencode.ai/config.json",
+  "mcp": {
+    "qdrant_memory": {
+      "type": "local",
+      "command": ["uvx", "--from", "qdrant-memory-mcp==0.1.0", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
+      "enabled": true
+    }
+  }
+}
+```
+
+Pi needs a separately installed MCP client/extension. In that extension, use
+`command: uvx` and the same argument list. No built-in Pi MCP support or universal
+extension config format is claimed. These are configuration examples; this
+distribution's acceptance tests use the official Python MCP SDK, not live agent
+applications. See the Runtime's [client evidence and limits](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/mcp.md).
+
+## Tools and boundaries
+
+| Tool | Input | Result |
+|---|---|---|
+| `qdrant_memory_search` | `query`, optional `category` | Scoped memories with IDs, scores and provenance |
+| `qdrant_memory_add` | `text` | Durable memory ID |
+| `qdrant_memory_update` | exact `id`, replacement `text` | Scoped replacement |
+| `qdrant_memory_delete` | exact `id` | Scoped deletion |
+
+Scope is fixed by the operator's profile (`user_id`, `agent_id`). Model inputs
+and MCP client identity cannot override it; knowing an ID does not grant access.
+Migration, export, reset and bulk deletion remain trusted operator CLI commands;
+see [standalone maintenance](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/standalone.md).
+No resources or prompts are advertised. This is a local subprocess, with no
+public HTTP/SSE listener or remote authentication service. Stdout is reserved
+for protocol messages, with sanitized diagnostics on stderr.
+
+Data flows from client → Runtime → embedding provider → Qdrant and the local
+SQLite ledger. With local Ollama and embedded Qdrant, memory processing stays
+local; cloud embedding receives memory/query text, and cloud Qdrant receives
+vectors and stored payloads. The client/model may also receive recalled text.
+The operator must authorize retention and access and protect the profile files.
+
+One writer lease coordinates a profile/destination. Do not overlap MCP, CLI
+or Hermes processes writing to it. Separate profiles or machines do not provide
+a distributed lock. This package does not support uncoordinated multiprocess
+writes, auto-extraction, an HTTP transport, or implicit credential discovery
+from Hermes. It preserves the Runtime's ledger, IDs and recovery semantics.
+
+## Verification and development
+
+CI builds wheel/sdist, checks metadata and ownership marker, and runs installed
+protocol tests with temporary profiles, embedded Qdrant and a deterministic
+loopback embedding fixture on Linux/macOS/Windows, Python 3.11 and 3.14.
+No test connects to personal Qdrant, Hermes profiles or memory data. These tests
+cover initialize, discovery, four tools, persistence, recovery, scope isolation,
+error redaction and protocol stdout. Provider/cloud compatibility evidence
+belongs to the [Runtime](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/validation.md).
+
+CI prefers the immutable Runtime PyPI release. Before Runtime 0.2.0 reaches PyPI,
+CI builds a wheel from an immutable candidate
+commit recorded in `runtime-source.json`. This is only a preparation fixture:
+published dependency metadata always uses the exact PyPI version. Release
+workflow acceptance requires installation from PyPI and never uses that fallback.
+
+See [CI and dependency maintenance](docs/ci.md), [publishing](docs/publishing.md), [architecture](docs/architecture.md), and
+the optional [Skill](https://github.com/cnkang/skills/tree/main/qdrant-memory).

qdrant_memory_mcp-0.1.0.dist-info/RECORD

@@ -0,0 +1,6 @@
+qdrant_memory_mcp-0.1.0.dist-info/licenses/LICENSE,sha256=tI3MOOwKR6ncyQZfZF_QsRjB8_yoGYttXJp5oeLlqZQ,1065
+qdrant_memory_mcp-0.1.0.dist-info/METADATA,sha256=VmrBkKcFfOYJ-4CmrfPTZjTNINdS39HN7uWf_-QX9PY,8149
+qdrant_memory_mcp-0.1.0.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+qdrant_memory_mcp-0.1.0.dist-info/entry_points.txt,sha256=64_yXmNAAfk6PJaYblxeXVbiTNjP42nE8uxPZztu8YE,68
+qdrant_memory_mcp-0.1.0.dist-info/top_level.txt,sha256=AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs,1
+qdrant_memory_mcp-0.1.0.dist-info/RECORD,,

qdrant_memory_mcp-0.1.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

qdrant_memory_mcp-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+qdrant-memory-mcp = qdrant_memory.standalone:main

qdrant_memory_mcp-0.1.0.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Kang Liu
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

qdrant_memory_mcp-0.1.0.dist-info/top_level.txt

@@ -0,0 +1 @@
+