cnkang/qdrant-memory-mcp

One Memory. Multiple Agents.
Durable, portable, and permission-aware memory for AI agents — distributed as
an MCP adapter over the Qdrant Memory Runtime.
For shared production deployments, read the deployment security guide. Owner-only database write credentials are required independently of MCP grants. Runtime 0.5.0 includes destination protection and shared doctor. The operator must configure these controls. See the Owner support record for support limits.
## One Memory, Multiple Agents — opt-in shared owner
The distribution adds an opt-in single-owner service and stdio bridge. Install Runtime 0.5.4 to use them. See shared integration guide. Private defaults are unchanged. Native Provider automatic shared extraction is deferred.
A WorkBuddy connector and a
DeepSeek Harness bundle reuse this stdio
MCP, the managed launcher and the canonical Skill.
简体中文
Persistent, scoped memory for AI agents through four explicit stdio MCP tools.
This repository distributes the existing Python Runtime.
Its metadata-only wheel contains no Python business implementation. The console
script points directly to qdrantmemory.standalone:main and depends on
hermes-plugin-qdrant-memory[mcp]==0.5.4.
See 0.2.8 release notes for the Runtime pin and upgrade guidance.
Before using an exact-version installation command, confirm that version on
the PyPI release page.
Versions: MCP distribution 0.2.8 pins Runtime 0.5.4, which supports MCP
Python SDK 1.x and 2.x (mcp>=1.30,<3). The four scoped tools and stdio
launch arguments are the same for both SDK majors. It retains the fix for explicit
writes of distinct, highly similar texts without an LLM. The commands below use
these exact versions. Release
artifacts are available through the distribution PyPI page
and Runtime PyPI page.
See release checklist for the publishing sequence.
Runtime, optional Agent Skill
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.
## Harness support matrix
Verification levels: configuration example only, protocol-level tested, official
SDK/CLI tested, real host tested, real desktop GUI tested, not verified.
| Host | Native Provider | Explicit MCP tools | Automatic capture | Automatic recall | Shared Owner | Remote access | Verification |
| Hermes | Yes | Yes (via standalone) | Yes | Yes | Opt-in | Yes | Real host tested |
| OpenCode | No | Yes | No | No | Via Owner | Yes | Real host tested (dual-device) |
| Pi | No | Yes (extension) | Opt-in adapter | Opt-in adapter | Via Owner | Yes | Real host tested |
| DeepSeek Harness | No | Yes (DSH bundle) | No | No | Via Owner | Yes | Real host tested |
| WorkBuddy | No | Yes (connector) | No | No | Via Owner | Yes | Real desktop GUI tested |
| Codex | No | Yes | No | No | Via Owner | Yes | Configuration example only |
This distribution does not auto-extract conversations for any MCP host. Automatic
capture and recall require a native provider or a lifecycle adapter.
## Install and initialize