C
chinwe/compound-memory
Local multi-agent shared memory with compounding — MCP server + CLI
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"chinwe-compound-memory": {
"command": "uvx",
"args": ["--from", "compound-memory", "compound-memory-server"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"chinwe-compound-memory": {
"command": "uvx",
"args": ["--from", "compound-memory", "compound-memory-server"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio chinwe-compound-memory -- uvx --from compound-memory compound-memory-server
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · chinwe/compound-memory · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 1 ★ · 23 sources · mcp
- Install
uvx --from compound-memory compound-memory-server
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx --from compound-memory compound-memory-server. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
chinwe/compound-memory；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# compound-memory
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
English | 简体中文
Local-first shared memory for multiple AI agents — plain Markdown files that compound in value as they are used. Memory lives on your disk as frontmatter-annotated Markdown, gets stronger with every confirmed use, decays into a revivable archive when neglected, and auto-commits to a local git history on every write.
## Why
Every agent session starts from zero: preferences get re-asked, project conventions get re-discovered, the same pitfall gets hit twice. compound-memory gives all your agents one shared store:
Local-first — nothing leaves your machine; memories are human-readable Markdown files, not rows in an opaque database.
MCP-native — exactly 5 tools (memorywrite / memorysearch / memoryget / memorylink / memoryfeedback) as the single read-write boundary; works with any MCP host (Claude Code, ZCode, WorkBuddy, …), plus a full CLI for operations.
Compounding — confirmed usage raises confidence, related memories are recalled as neighbors, validation from a different host counts as independent evidence, and distillation merges many raw memories into fewer, denser ones.
Multi-agent by design — a shared namespace everyone reads, plus agent- private namespaces each host owns; cross-host validation is tracked per host.
Optional semantic recall — vector search via sqlite-vec + BGE embeddings, with automatic graceful fallback to pure lexical search when unavailable. Override the model with COMPOUNDMEMORYEMBEDDINGMODEL (default Xenova/bge-small-zh-v1.5) and COMPOUNDMEMORYEMBEDDINGDIM (default 512); changing either is an ops action and needs an explicit rebuild-index.
## Quick Start
### For AI agents
Paste this one-liner into your coding agent (Claude Code, Cursor, ZCode, …) and let it do the rest:
text
Set up compound-memory (https://github.com/chinwe/compound-memory) — a local-first multi-agent shared memory (MCP server + CLI) — on this machine. Do not clone the repo for a normal install. Initialize the store with uvx --from compound-memory compound-memory init (defaults to ~/.agents/memory). Register its stdio MCP server in this host's MCP config: command uvx, args --from compound-memory compound-memory-server, env COMPOUNDMEMORYROOT=$HOME/.agents/memory and COMPOUNDMEMORYAGENTID=agent- . Verify by calling memorysearch and expecting a {"hits": [...]} response; if the host needs a restart to load MCP servers, tell me. Use uv run --directory only when developing against a local checkout. Short English setup and the search → feedback → write loop: docs/agent-integration.en.md. Full per-host configs: docs/agent-integration.md.
### For humans
#### 1. Install
Python ≥ 3.11. The default does not clone the repo:
bash
# Default: PyPI. Hosts launch the MCP server with
# uvx --from compound-memory compound-memory-server
# Optional CLI on PATH:
uv tool install compound-memory # or: pip install compound-memory
# Developer / local checkout only — not the default host launch
git clone https://github.com/chinwe/compound-memory.git
cd compound-memory && uv sync --extra dev
#### 2. Initialize your store
Defaults to ~/.agents/memory; override with the COMPOUNDMEMORYROOT env var. A leading ~ or $HOME is expanded; a blank override falls back to the default.
Local-first shared memory for multiple AI agents — plain Markdown files that compound in value as they are used. Memory lives on your disk as frontmatter-annotated Markdown, gets stronger with every confirmed use, decays into a revivable archive when neglected, and auto-commits to a local git history on every write.
## Why
Every agent session starts from zero: preferences get re-asked, project conventions get re-discovered, the same pitfall gets hit twice. compound-memory gives all your agents one shared store:
Local-first — nothing leaves your machine; memories are human-readable Markdown files, not rows in an opaque database.
MCP-native — exactly 5 tools (memorywrite / memorysearch / memoryget / memorylink / memoryfeedback) as the single read-write boundary; works with any MCP host (Claude Code, ZCode, WorkBuddy, …), plus a full CLI for operations.
Compounding — confirmed usage raises confidence, related memories are recalled as neighbors, validation from a different host counts as independent evidence, and distillation merges many raw memories into fewer, denser ones.
Multi-agent by design — a shared namespace everyone reads, plus agent- private namespaces each host owns; cross-host validation is tracked per host.
Optional semantic recall — vector search via sqlite-vec + BGE embeddings, with automatic graceful fallback to pure lexical search when unavailable. Override the model with COMPOUNDMEMORYEMBEDDINGMODEL (default Xenova/bge-small-zh-v1.5) and COMPOUNDMEMORYEMBEDDINGDIM (default 512); changing either is an ops action and needs an explicit rebuild-index.
## Quick Start
### For AI agents
Paste this one-liner into your coding agent (Claude Code, Cursor, ZCode, …) and let it do the rest:
text
Set up compound-memory (https://github.com/chinwe/compound-memory) — a local-first multi-agent shared memory (MCP server + CLI) — on this machine. Do not clone the repo for a normal install. Initialize the store with uvx --from compound-memory compound-memory init (defaults to ~/.agents/memory). Register its stdio MCP server in this host's MCP config: command uvx, args --from compound-memory compound-memory-server, env COMPOUNDMEMORYROOT=$HOME/.agents/memory and COMPOUNDMEMORYAGENTID=agent- . Verify by calling memorysearch and expecting a {"hits": [...]} response; if the host needs a restart to load MCP servers, tell me. Use uv run --directory only when developing against a local checkout. Short English setup and the search → feedback → write loop: docs/agent-integration.en.md. Full per-host configs: docs/agent-integration.md.
### For humans
#### 1. Install
Python ≥ 3.11. The default does not clone the repo:
bash
# Default: PyPI. Hosts launch the MCP server with
# uvx --from compound-memory compound-memory-server
# Optional CLI on PATH:
uv tool install compound-memory # or: pip install compound-memory
# Developer / local checkout only — not the default host launch
git clone https://github.com/chinwe/compound-memory.git
cd compound-memory && uv sync --extra dev
#### 2. Initialize your store
Defaults to ~/.agents/memory; override with the COMPOUNDMEMORYROOT env var. A leading ~ or $HOME is expanded; a blank override falls back to the default.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/chinwe-compound-memory/)
- Source
- awesome · https://github.com/chinwe/compound-memory
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.