save_contextLABSCO SUMMARY
A context store its own author has retired.
Four calls, two shapes of context and a tag index — enough to hand an assistant a project's history and get it back next session, with entries that can name what they continue. The author says so on the front page: it never went past v0.1.0, and Claude Code's native memory files and CLAUDE.md now cover the same ground. Read it if you are building a context store of your own; look elsewhere if you want one that is still being maintained.
What it is
A stdio server that gives an assistant somewhere to put context between sessions. Two shapes go in: project context, which carries a project id and can point at a parent context and at related entries, and conversation context, which carries a session id and can mark itself the continuation of an earlier one. Both are tagged, stored as JSON on your own disk, and read back by id or listed by project, tag or kind. Its author archived the project in March 2026, naming Claude Code's own memory files and CLAUDE.md as having taken the job over.
What you get
- Project context saved under a project id, with an optional parent context and a list of related context ids
- Conversation context saved under a session id, optionally marked as the continuation of a previous one
- Free-form tags and a metadata object on every entry
- Any entry retrieved by id, scoped to its project when you have one
- Entries listed and filtered by project, by tag, or by kind — project or conversation
Requirements
Node, and the repository itself: the compiled server is committed alongside the source, so it runs from the checkout. No account and no key — contexts are JSON files on your own disk, under a directory the server creates. The project is archived and stopped at v0.1.0, so what is in the repository is the finished shape.
Setup effort
Build from source — git clone https://github.com/davidteren/claude-server.git
USE CASES
01
Carrying a project's decisions into next week
Save what was agreed under the project id with tags, and read it back by id when the work resumes.
02
Picking a conversation back up
Store the session's context marked as continuing the previous one, then find it again by listing what belongs to that session.
03
Pulling together everything on one topic
List contexts filtered by tag across projects and sessions, then retrieve the ones that matter.
04
Keeping a chain of related notes
Point a new project context at its parent and at related entries, so what follows from what is recorded rather than remembered.
5 tools
Listed in project docs. Your client may show a different list.
save_project_contextsave_conversation_contextget_contextlist_contextsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
Node.js and npm
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/davidteren/claude-server.git
cd claude-server
npm installMCP Clients
Claude Desktop
After installing, add this to ~/Library/Application Support/Claude/claude_desktop_config.json. <YOUR_PATH_TO_CLAUDE_SERVER> is the folder you cloned into.
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"claude-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_CLAUDE_SERVER>/build/index.js"
]
}
}
}
