B
botzrDev/dreamd
Portable, local-first memory layer for AI coding agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Official descriptionPortable, local-first memory layer for AI coding agents. One .agent/ folder shared across Claude Code, Cursor and Cline over MCP. Plain files, no vector DB.
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"botzrdev-dreamd": {
"command": "npx",
"args": ["-y", "dreamd-mcp"]
}
}
}Parsed from the README we fetched on 2026-10-29; 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": {
"botzrdev-dreamd": {
"command": "npx",
"args": ["-y", "dreamd-mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio botzrdev-dreamd -- npx -y dreamd-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 6 ★ · botzrDev/dreamd · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-29 · last seen 2026-11-14 · seen 17× · listed by 1 sources
- Score
- score 103 · 6 ★ · 1 sources · repo
- Install
npx -y dreamd-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y dreamd-mcp. 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: 记忆增强. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
botzrDev/dreamd；first catalogued 2026-10-29；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# dreamd
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The plain files in your repo are the memory. dreamd is the local server that reads and writes them.
Drop a .agent/ folder in the project. Claude Code, Cursor, Cline, and other MCP-aware harnesses share it. What one agent learns, the next already knows. You can cat, grep, and git diff every byte. Durable appends go through MCP / the daemon so the writer stays single-writer.
This is not "another memory product." It is a storage-model wedge: the filesystem is the source of truth, and the MCP tools (searchnodes / appendnode) are a thin interface over those files.
Open core: Apache-2.0 core today, self-hosted only. Premium features may ship later. Do not read this as free-forever for everything.
bash
npx -y dreamd-mcp setup # scaffold .agent/ and wire your harness
npx -y dreamd-mcp # MCP server (stdio) — what the harness spawns
> First run prints a local-only privacy disclosure. setup prompts for harness choice when it has a TTY.
## The moment it earns its name
Recorded live, sped up 1.5x: Claude Code writes the lesson, OpenCode reads it back through the same .agent/ folder. Tape: docs/assets/demo.tape.
No re-explaining. No re-pasting. Same .agent/ folder, every harness.
## Install
### npm (recommended)
bash
npx -y dreamd-mcp setup # scaffold .agent/ + write the harness MCP config
npx -y dreamd-mcp # MCP server (stdio) — your harness spawns this
stdio stays the default transport. dreamd mcp --bind 127.0.0.1: is the opt-in Streamable HTTP server at /mcp. It is unauthenticated, and it is only in source builds with --features mcp-http — see docs/mcp-transports.md.
Requires a project root sentinel (.git/, Cargo.toml, package.json, or pyproject.toml).
setup prompts when it has a TTY. In scripts and non-interactive shells, pass --yes --harness claude|cursor|both (--harness none or --no-write-mcp scaffolds without touching any MCP config).
### Cargo / from source
bash
git clone https://github.com/botzrDev/dreamd.git
cd dreamd
cargo install --path crates/dreamd-cli
See CONTRIBUTING.md for the full dev setup.
## Quick start ( on the npm path, or cargo install --path crates/dreamd-cli if you want the dreamd binary. The shim forwards only some subcommands (npx -y dreamd-mcp --help lists them); recall, score, status, archive, and migrate need the dreamd binary.
Adapters: Claude Code · Cursor · Cline
## What dreamd writes
| Location | Contents | Commit? |
| /.agent/ | Episodic JSONL, semantic lessons, personal prefs | Yes (this is the shared memory) |
| /.agent/.dreamd/ | Local index, daemon state, config template, memory branches, provenance ledger | No (gitignored by init) |
| ~/.agent/registry.toml | Which projects have a store | No |
| ~/.agent/dreamd.sock | Daemon API socket (while running) | No |
npx -y dreamd-mcp setup (or dreamd setup after a cargo install) scaffolds the store by calling init, then writes the harness MCP config. init is the scaffold primitive and still works on its own when you want the store without touching any MCP config. Both are idempotent. To uninstall from a machine — stop local servers, remove the socket, unregister the current project, clear caches — run npx -y dreamd-mcp uninstall (project .agent/ stores are left in place). Advanced, registry-only: npx -y dreamd-mcp init --uninstall-project unregisters the current project and touches nothing else.
Drop a .agent/ folder in the project. Claude Code, Cursor, Cline, and other MCP-aware harnesses share it. What one agent learns, the next already knows. You can cat, grep, and git diff every byte. Durable appends go through MCP / the daemon so the writer stays single-writer.
This is not "another memory product." It is a storage-model wedge: the filesystem is the source of truth, and the MCP tools (searchnodes / appendnode) are a thin interface over those files.
Open core: Apache-2.0 core today, self-hosted only. Premium features may ship later. Do not read this as free-forever for everything.
bash
npx -y dreamd-mcp setup # scaffold .agent/ and wire your harness
npx -y dreamd-mcp # MCP server (stdio) — what the harness spawns
> First run prints a local-only privacy disclosure. setup prompts for harness choice when it has a TTY.
## The moment it earns its name
Recorded live, sped up 1.5x: Claude Code writes the lesson, OpenCode reads it back through the same .agent/ folder. Tape: docs/assets/demo.tape.
No re-explaining. No re-pasting. Same .agent/ folder, every harness.
## Install
### npm (recommended)
bash
npx -y dreamd-mcp setup # scaffold .agent/ + write the harness MCP config
npx -y dreamd-mcp # MCP server (stdio) — your harness spawns this
stdio stays the default transport. dreamd mcp --bind 127.0.0.1: is the opt-in Streamable HTTP server at /mcp. It is unauthenticated, and it is only in source builds with --features mcp-http — see docs/mcp-transports.md.
Requires a project root sentinel (.git/, Cargo.toml, package.json, or pyproject.toml).
setup prompts when it has a TTY. In scripts and non-interactive shells, pass --yes --harness claude|cursor|both (--harness none or --no-write-mcp scaffolds without touching any MCP config).
### Cargo / from source
bash
git clone https://github.com/botzrDev/dreamd.git
cd dreamd
cargo install --path crates/dreamd-cli
See CONTRIBUTING.md for the full dev setup.
## Quick start ( on the npm path, or cargo install --path crates/dreamd-cli if you want the dreamd binary. The shim forwards only some subcommands (npx -y dreamd-mcp --help lists them); recall, score, status, archive, and migrate need the dreamd binary.
Adapters: Claude Code · Cursor · Cline
## What dreamd writes
| Location | Contents | Commit? |
| /.agent/ | Episodic JSONL, semantic lessons, personal prefs | Yes (this is the shared memory) |
| /.agent/.dreamd/ | Local index, daemon state, config template, memory branches, provenance ledger | No (gitignored by init) |
| ~/.agent/registry.toml | Which projects have a store | No |
| ~/.agent/dreamd.sock | Daemon API socket (while running) | No |
npx -y dreamd-mcp setup (or dreamd setup after a cargo install) scaffolds the store by calling init, then writes the harness MCP config. init is the scaffold primitive and still works on its own when you want the store without touching any MCP config. Both are idempotent. To uninstall from a machine — stop local servers, remove the socket, unregister the current project, clear caches — run npx -y dreamd-mcp uninstall (project .agent/ stores are left in place). Advanced, registry-only: npx -y dreamd-mcp init --uninstall-project unregisters the current project and touches nothing else.
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/botzrdev-dreamd/)
- Source
- github · https://github.com/botzrDev/dreamd
- Browse by field
- Memory & context
- Traction
- 6 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.