Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
MEMORY_FILE_PATH=<value> claude mcp add io.github.zamansheikh-memory-lean -- npx -y memory-lean@1.6.1In einem Terminal ausführen.
{ "mcpServers": { "io.github.zamansheikh-memory-lean": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "MEMORY_FILE_PATH": "<value>" } } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
About 40× smaller answers. Search returns a ranked list of names and the lines that matched, not every entity in full, so the agent can afford to check its memory before every task.
A web UI for people. See the whole graph grouped by type, follow relations, and add, edit or delete anything. Agent writes show up live.
Token-lean memory for AI agents: a knowledge graph searched cheaply. Drop-in for server-memory.
Drop-in replacement. Same memory.jsonl file and the same nine tools as the
reference server. Switch in, and switch back whenever you like.
Works with every agent. Copy-paste setup for Claude Code, MiMo Code, Codex, Cursor, Copilot, Gemini CLI, Zed, JetBrains and more, plus the instructions that teach the agent to use it.
Stays small by itself. Short facts, a cap per entity, and an archive for the overflow, so the graph never grows into a wall of text.
Private and safe. Plain local files, daily backups, a write lock for parallel sessions, and no network access. One server file, zero dependencies.
Measured on a real graph of 237 entities, 355 relations and 1,160 facts (tokens ≈ characters ÷ 4):
A narrow search that matches one or two entities saves less, because there is
little to trim. To measure your own graph, run node tools/bench.mjs from a clone;
it is read-only and prints sizes, never content.
Claude Code: install the plugin. It adds the server, the instructions as a
skill, a short reminder at the start of each session, and /memory-ui.
/plugin marketplace add zamansheikh/memory-lean
/plugin install memory-lean@memory-lean
Any other agent: add the server to its MCP config, then give it the instructions.
{
"mcpServers": {
"memory": { "command": "npx", "args": ["-y", "memory-lean"] }
}
}
npx -y memory-lean --protocol >> AGENTS.md # into the rules file your agent reads
Just looking? Open the web UI on a made-up example graph:
npx -y memory-lean --ui --demo
The graph is created on the first write at ~/.claude/memory-graph/memory.jsonl,
whichever agent writes it, so all your agents share one memory. Set
MEMORY_FILE_PATH to keep it somewhere else.
npx -y memory-lean --ui
This opens your memory in the browser. Everything an agent can do, you can do here:
The page runs on your machine only (127.0.0.1) and needs the one-time key in
the link it prints, so other websites cannot read or change your memory. Nothing
is uploaded anywhere.
The reference server answers a search with every matching entity in full, as pretty-printed JSON. memory-lean answers with a ranked list of names and the lines that matched:
> search_nodes { "query": "deploy" }
57 match "deploy", top 10 shown (narrow the query or raise limit). open_nodes for full entities.
- shop-backend [service] 12 obs, 6 rel
› 2026-03-02: deployed 2.4.0 to production
› deploy with scripts/release.sh, never by hand
- PENDING shop-backend 2.4.0 [pending] 2 obs, 3 rel
› …mobile apps still call the old endpoint until the deploy of 2.4.0 reaches them
The agent then opens only what it needs:
> open_nodes { "names": ["shop-backend"] }
## shop-backend [service] (3 archived)
- NestJS API behind api.example.com
- 2026-03-02: deployed 2.4.0 to production
## relations
shop-app -talks_to-> shop-backend
PENDING shop-backend 2.4.0 -blocks-> shop-app
The three read tools are marked read-only, so clients that support it can run them without asking.
With npx, put npx -y in front: npx -y memory-lean --ui.
A memory server only helps if the agent reads it before working and writes to it
when something changes. docs/AGENT-PROTOCOL.md is a
ready-made set of instructions: what to look up at the start of a task, what to
record, how to name things, and what never to store. The Claude Code plugin
includes it. For every other agent, one command installs it:
npx -y memory-lean --protocol >> AGENTS.md # into a rules file: always on
npx -y memory-lean --skill .agents/skills # as an Agent Skill: loaded when relevant
Adjust the entity types and names in it to your own work.
Point MEMORY_FILE_PATH at your existing memory.jsonl and swap the command. The
file format is identical, so you can switch back at any time. Existing
observations longer than 300 characters are kept as they are; only new writes are
checked. To see what is over budget, and optionally fix it:
npx -y memory-lean --lint # report only
npx -y memory-lean --compact # back up, then move overflow to archive/
All optional, set as environment variables on the server:
No. The server reads and writes local files and makes no network requests. The web UI listens on 127.0.0.1 only. Keep the graph out of git, and never store passwords, keys or tokens in it: record where a secret lives, not its value.
Yes. Every write takes a lock, re-reads the file and replaces it atomically, so parallel sessions (and the web UI) do not overwrite each other.
It needs no model, no index and no dependencies, and an agent's queries are mostly names it already knows. Good entity names matter more than clever queries.
When an entity passes 15 facts, the oldest dated ones move to archive/<entity>.md next to the graph. archived_observations, or the Archive section in the web UI, lists and restores them.
/memory-uirename_entity and archive restoreIdeas, bug reports and pull requests are welcome. The server is one file with no
dependencies, the web UI is one HTML file, and npm test runs in a few seconds,
so a first change is quick to make. CONTRIBUTING.md has the
layout, the ground rules and a list of good first contributions.
If memory-lean saves you tokens, a ⭐ helps other people find it.
memory-lean is free and MIT licensed. If it is useful to you, you can support the work:
Created and maintained by Zaman Sheikh at Silifton.
Built on the file format and tool names of the Model Context Protocol reference memory server.
MIT © 2026 Zaman Sheikh. Free to use, change and share, including commercially; keep the copyright notice.
Token-lean memory for AI agents: a knowledge graph searched cheaply. Drop-in for server-memory.
{ "mcpServers": { "io.github.zamansheikh-memory-lean": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "MEMORY_FILE_PATH": "<value>" } } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: MEMORY_FILE_PATH.
Memory Lean läuft lokal über stdio.
Zuletzt geprüft: 2026-11-14. Token-lean memory for AI agents: a knowledge graph searched cheaply. Drop-in for server-memory.